SymfonyFramework / library · Sensiolabs
CVE-2013-1397
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 · uneditedSymfony 2.0.x before 2.0.22, 2.1.x before 2.1.7, and 2.2.x remote attackers to execute arbitrary PHP code via a serialized PHP object to the (1) Yaml::parse or (2) Yaml\Parser::parse function, a different vulnerability than CVE-2013-1348.
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 confidenceSymfony's Yaml::parse and Yaml\Parser::parse functions are vulnerable to PHP object injection via crafted serialized PHP objects in YAML input, allowing remote attackers to execute arbitrary PHP code. This affects Symfony 2.0.x before 2.0.22, 2.1.x before 2.1.7, and 2.2.x.
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
SymfonyFramework / library
= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10= 2.0.11CVSS 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 Symfony versionLocate the Symfony version file (e.g., vendor/symfony/http-kernel/Symfony/Component/HttpKernel/Kernel.php or composer.lock) and read the version constant, or run 'composer show symfony/symfony' to list installed versionAffected if The installed version is 2.0.0 through 2.0.21, 2.1.0 through 2.1.6, or any 2.2.x version before checking if the Yaml component is in use
-
Verify Yaml component is installedCheck for the presence of vendor/symfony/yaml/ or run 'composer show symfony/yaml' to confirm the Yaml component is installed as a dependencyAffected if The Yaml component exists in the vendor directory and its version matches the vulnerable Symfony version ranges above
-
Detect YAML parsing usage in application codeSearch source code for calls to Yaml::parse() or Yaml\Parser::parse() - use grep or a code search for 'Yaml::parse' or 'Yaml\\Parser::parse' across PHP filesAffected if Code actively calls the parse function on YAML input, creating the attack surface for object injection
-
Identify source of YAML inputReview application code that parses YAML to determine if input comes from user-uploaded files, API payloads, external APIs, or other untrusted sources rather than only from trusted internal configuration filesAffected if The application parses YAML data from untrusted sources (user input, HTTP requests, uploaded files) using the vulnerable parse methods
A system is affected if it runs a vulnerable Symfony version (2.0.x before 2.0.22, 2.1.x before 2.1.7, or 2.2.x) AND uses the Yaml component to parse potentially untrusted YAML input.
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 dataUpgrade Symfony to version 2.0.22, 2.1.7, 2.2.0 or later to patch the unsafe YAML deserialization vulnerability.
Fix this in Symfony
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1397 — 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-2013-1397 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