SpoonApplication · Ingy
CVE-2012-6143
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 · uneditedSpoon::Cookie in the Spoon module 0.24 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 confidenceThe Spoon::Cookie module in Spoon 0.24 for Perl insecurely deserializes cookie data using Storable::thaw without validating the input first. Since Storable can execute code references during deserialization, an attacker can craft malicious serialized data in a cookie to achieve arbitrary code execution on the server.
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
SpoonApplication
= 0.24CVSS 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.
-
Check if Spoon module is installedRun 'perl -MSpoon -e "print $Spoon::VERSION"' or check via 'cpan -l' or your system's package managerAffected if Spoon version 0.24 is installed
-
Verify Spoon::Cookie is in useSearch your application code for 'use Spoon::Cookie' or 'require Spoon::Cookie' statementsAffected if Your code explicitly loads or uses Spoon::Cookie
-
Identify cookie handling codeSearch your codebase for calls to Storable::thaw or Spoon::Cookie methods that deserialize cookie values (such as any 'thaw' method on cookie objects)Affected if Code passes cookie data through Storable::thaw for deserialization without prior validation
-
Check for input validation on cookie dataInspect the cookie deserialization logic to determine if any validation (length checks, format validation, cryptographic signature verification) occurs before Storable::thaw is calledAffected if Cookie values are directly fed to Storable::thaw without validation or signature verification
You are affected if you run Spoon 0.24 and your application uses Spoon::Cookie to deserialize cookie data via Storable::thaw without validating the cookie values beforehand.
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 dataReplace or wrap Storable::thaw with safe deserialization that validates input before processing, or implement a cryptographic signature/mac on cookie values to ensure they haven't been tampered with before deserialization.
Fix this in Spoon
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6143 — 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-2012-6143 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