Debian LinuxOperating system · Debian
CVE-2015-1592
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 · uneditedMovable Type Pro, Open Source, and Advanced before 5.2.12 and Pro and Advanced 6.0.x before 6.0.7 does not properly use the Perl Storable::thaw function, which allows remote attackers to include and execute arbitrary local Perl files and possibly execute arbitrary code via unspecified vectors.
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 confidenceMovable Type improperly uses Perl's Storable::thaw function for deserialization, allowing remote attackers to inject and execute arbitrary local Perl files or achieve arbitrary code execution through deserialization of untrusted data.
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>= 5.2.0, < 5.2.12>= 6.0, < 6.0.7CVSS 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
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Movable Type versionCheck the version file in your Movable Type installation directory, typically found in a version.pm or mt-config.cgi file, or look for a version indicator in the MT administration interfaceAffected if The installed version is 5.2.0 through 5.2.11, or 6.0.0 through 6.0.6 (versions below 5.2.12 or 6.0.7)
-
Verify Debian versionRun 'cat /etc/debian_version' or 'lsb_release -a' to determine if the system is running Debian 7.0Affected if The system is running Debian Linux 7.0 with a vulnerable Movable Type installation
-
Locate Movable Type Perl modulesSearch for Storable.pm in the Movable Type installation directory, typically under the 'lib' or 'extlib' folder, using 'find <mt_directory> -name 'Storable.pm'Affected if The Storable Perl module is present and loaded by Movable Type
-
Check for deserialization usageSearch Movable Type source files for 'thaw' function calls, particularly in CGI or request handling code, using 'grep -r "thaw" <mt_directory>'Affected if The application uses Storable::thaw to deserialize data, especially from untrusted sources like user input or cookies
You are affected if Movable Type version is below 5.2.12 (5.x branch) or below 6.0.7 (6.x branch) and the application deserializes data using Perl's Storable::thaw function.
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 data5.2.126.0.7
Upgrade Movable Type to version 5.2.12 or later, or 6.0.7 or later for the 6.x branch, to patch the vulnerable Storable::thaw implementation.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1592 — 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-1592 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