CVE-2011-1584
What it is
The updateFile function in inc/core/class.dc.media.php in the Media Manager in Dotclear before 2.2.3 does not properly restrict pathnames, which allows remote authenticated users to upload and execute arbitrary PHP code via the media_path or media_file parameter. NOTE: some of these details are obtained from third party information.
At a glance
- Exploitability
- Can be exploited over the network with a login. Limited direct impact.
- Exploit odds
- 1.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.7% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.7% · EPSS, next 30 days
- Weakness
- CWE-264
- Record status
- Modified
Affected
- Dotclear ≤ 2.2.2
- Dotclear 1.2.1
- Dotclear 1.2.2
- Dotclear 1.2.3
- Dotclear 1.2.4
- Dotclear 1.2.5
- Dotclear 1.2.6
- Dotclear 1.2.7
Attack profile CVSS 2.0 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:S/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2011-1584.md and follow it. Check whether this project is affected by CVE-2011-1584. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://dev.dotclear.org/2.0/changeset/2:3427
- http://dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://fr.dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://secunia.com/advisories/44049
- http://dev.dotclear.org/2.0/changeset/2:3427
- http://dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://fr.dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://secunia.com/advisories/44049
References
- http://dev.dotclear.org/2.0/changeset/2:3427
- http://dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://fr.dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://openwall.com/lists/oss-security/2011/04/13/19
- http://openwall.com/lists/oss-security/2011/04/14/8
- http://openwall.com/lists/oss-security/2011/04/15/11
- http://openwall.com/lists/oss-security/2011/04/15/7
- http://secunia.com/advisories/44049
- http://www.arcabit.com/english/home/a-flaw-in-dotclear
- http://dev.dotclear.org/2.0/changeset/2:3427
- http://dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://fr.dotclear.org/blog/post/2011/04/01/Dotclear-2.2.3
- http://openwall.com/lists/oss-security/2011/04/13/19
- http://openwall.com/lists/oss-security/2011/04/14/8
- http://openwall.com/lists/oss-security/2011/04/15/11
- http://openwall.com/lists/oss-security/2011/04/15/7
- http://secunia.com/advisories/44049
- http://www.arcabit.com/english/home/a-flaw-in-dotclear