CVE-2014-125112
Miyagawa Plack\ \
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2014-125112 is a critical-severity Reliance on Cookies without Validation and Integrity Checking (CWE-565) vulnerability in Miyagawa Plack\. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2014-125112 is a remote code execution vulnerability in Plack::Middleware::Session::Cookie versions through 0.21 for Perl. The flaw occurs during deserialization of cookie data when no secret is used to sign the cookie, allowing attackers to inject and execute arbitrary code on the affected server. It has a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-565 (Reliance on Cookies without Validation and Integrity Checking).
A remote, unauthenticated attacker can exploit this vulnerability by sending a specially crafted cookie to a vulnerable application. No user interaction or privileges are required, and exploitation requires low complexity over the network. Successful exploitation grants the attacker full control over the server, enabling high-impact compromise of confidentiality, integrity, and availability through arbitrary code execution.
Advisories and release notes, including a GitHub Gist by the maintainer, changes in Plack::Middleware::Session 0.23-TRIAL on MetaCPAN, and an oss-security mailing list post dated 2026-03-26, detail the issue and mitigation. Practitioners should update to Plack::Middleware::Session::Cookie version 0.23 or later, which addresses the deserialization flaw by enforcing proper signing.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2014-9820
Vulnerability Data
Plack::Middleware::Session::Cookie versions through 0.21 for Perl allows remote code execution. Plack::Middleware::Session::Cookie versions through 0.21 has a security vulnerability where it allows an attacker to execute arbitrary code on the server during deserialization of the cookie data, when there is no…
more
secret used to sign the cookie.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability enables remote unauthenticated arbitrary code execution via specially crafted cookies in a public-facing Plack middleware for Perl web applications, directly facilitating T1190: Exploit Public-Facing Application.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates the vulnerability by requiring timely remediation through updating to Plack::Middleware::Session::Cookie version 0.23 or later, which enforces proper cookie signing during deserialization.
Requires cryptographic mechanisms to verify the integrity of software and information such as session cookies, preventing execution of tampered deserialized data lacking a signing secret.
Mandates validation of information inputs like cookies to reject malformed or malicious serialized payloads before deserialization processing on the server.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Cookies commonly carry identity assertions; requiring their protection, conveyance, and verification directly eliminates the weakness.
Strong authentication mechanisms reduce reliance on unvalidated cookies for identity and access decisions.
Cryptographic integrity for data-in-transit directly mitigates tampering of cookies sent over the network.
Enforcing access policy and least privilege limits damage from cookie misuse but does not address cookie validation itself.
Integrity protections for data-at-rest can apply to cookie stores but do not cover validation during use.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect cookie-validation flaws but does not itself implement the required controls.
Application security requirements can mandate cookie validation, integrity protection, and server-side session handling.
Secure coding practices directly eliminate reliance on unvalidated cookies by requiring proper integrity checks and server-side verification.
Secure authentication mechanisms can enforce server-side validation and integrity checks that prevent reliance on untrusted cookies.