Debian LinuxOperating system · Debian
CVE-2015-5723
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDoctrine Annotations before 1.2.7, Cache before 1.3.2 and 1.4.x before 1.4.2, Common before 2.4.3 and 2.5.x before 2.5.1, ORM before 2.4.8 or 2.5.x before 2.5.1, MongoDB ODM before 1.0.2, and MongoDB ODM Bundle before 3.0.1 use world-writable permissions for cache directories, which allows local users to execute arbitrary PHP code with additional privileges by leveraging an application with the umask set to 0 and that executes cache entries as code.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple Doctrine libraries create cache directories with world-writable permissions (mode 0777), allowing local users to write arbitrary PHP code into cache files that the application then executes as code. This enables local privilege escalation when the application runs with a restrictive umask of 0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 7.0= 8.0<= 2.4.7= 2.5.0= 2.5.1= 2.5.2<= 2.4.7= 2.5.0= 3.0.0<= 2.4.7<= 1.12.15<= 2.4.2= 2.5.0<= 1.2.6<= 1.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Doctrine/Zend component versionsRun 'composer show doctrine/*' or check your composer.lock file for doctrine/annotations, doctrine/cache, doctrine/common, doctrine/orm, doctrine/mongodb-odm, and their versions. For Zend, check your vendor/zendframework directory.Affected if The installed version falls within: Annotations <= 1.2.6, Cache <= 2.4.7 or 2.5.0-2.5.2, Common <= 2.4.2 or 2.5.0, ORM <= 2.4.7 or 2.5.0, MongoDB ODM <= 1.0.1, or Zend Framework <= 2.4.7 or <= 1.12.15, or Zend Cache <= 2.4.7 or 2.5.0-2.5.2
-
Check application umask settingAdd this PHP code to your application temporarily: 'echo umask();' or check the umask setting where your PHP process is spawned. Look for umask(0) calls in your application bootstrap or entry point files.Affected if The umask is set to 0 (zero), which prevents the application from removing group/world write permissions from newly created directories and files
-
Inspect cache directory permissionsLocate your Doctrine/Zend cache directories (commonly in cache/ or data/cache under your app root, or in sys_get_temp_dir()). Run 'ls -la' on these directories and check the permission bits.Affected if Cache directories show permissions like drwxrwxrwx (0777) indicating they were created with world-writable permissions
-
Verify if application creates new cache filesTrigger cache generation in your application (e.g., clear cache then run a request that uses Doctrine metadata parsing or Zend caching). Then list files in the cache directory with 'ls -la'.Affected if Newly created cache files or directories have permissions 0777 (world-writable) due to the umask 0 setting combined with the vulnerable library code
You are affected if any Doctrine/Zend component version is in the affected list AND your cache directories or files are world-writable (0777) AND your application runs with umask 0, allowing local users to potentially inject executable PHP code into cache files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate all affected Doctrine components to patched versions (Annotations 1.2.7+, Cache 1.3.2+/1.4.2+, Common 2.4.3+/2.5.1+, ORM 2.4.8+/2.5.1+, MongoDB ODM 1.0.2+, MongoDB ODM Bundle 3.0.1+) and ensure the application umask is set appropriately (e.g., umask 022) to prevent overly permissive file permissions.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5723 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data