dbcve.org
Html\Application · Jochen Wiedmann

CVE-2012-6142

HIGH · 7.5 CVSS v2.0 Published 2014-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Session::Cookie in the HTML::EP module 0.2011 for Perl does not properly use the Storable::thaw function, which allows remote attackers to execute arbitrary code via a crafted request, which is not properly handled when it is deserialized.

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 confidence

The HTML::EP Perl module's Session::Cookie implementation improperly uses Storable::thaw for deserializing session data from cookies without proper validation, allowing remote attackers to inject malicious serialized objects that execute arbitrary code upon deserialization.

MitigationUpgrade to a patched version of HTML::EP or implement cryptographic signing/validation of cookie session data before deserialization using Storable::thaw to prevent tampering.

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
Html\Application
Affected:= \

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if HTML::EP is installed
    Run: perl -MHTML::EP -e 'print $HTML::EP::VERSION' 2>/dev/null || perldoc -l HTML::EP
    Affected if HTML::EP module is present on the system
  2. Identify the installed HTML::EP version
    Compare the version number from step 1 against the affected version range for this CVE
    Affected if The installed version falls within the vulnerable version range
  3. Determine if Session::Cookie is in use
    Search codebase and configuration files for 'Session::Cookie' or 'HTML::EP::Session::Cookie' usage patterns
    Affected if Session::Cookie is implemented for handling session data
  4. Check if cookie-based session handling is active
    Review application code or HTML::EP configuration for session cookie processing via Storable::thaw
    Affected if Session data from cookies is deserialized using Storable::thaw without additional validation

You are affected if HTML::EP with Session::Cookie is installed and configured to deserialize session data from cookies using Storable::thaw without cryptographic validation or signing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of HTML::EP or implement cryptographic signing/validation of cookie session data before deserialization using Storable::thaw to prevent tampering.

Fix this in Html\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-6142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-6142 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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