CVE-2012-5769
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 · uneditedIBM SPSS Modeler 14.0, 14.1, 14.2 through FP3, and 15.0 before FP2 allows remote attackers to read arbitrary files, and possibly send HTTP requests to intranet servers or cause a denial of service (CPU and memory consumption), via an XML external entity declaration in conjunction with an entity reference.
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 confidenceIBM SPSS Modeler contains an XML External Entity (XXE) vulnerability in its XML parser. By submitting malicious XML with external entity declarations, attackers can cause the application to read arbitrary files from the server, perform SSRF attacks against internal systems, or cause denial of service through resource exhaustion.
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= 14.0.0.0= 14.0.0.1= 14.0.0.2= 14.1.0.0= 14.1.0.1= 14.1.0.2= 14.2.0.0= 14.2.0.1= 14.2.0.2= 14.2.0.3= 15.0.0.0= 15.0.0.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:N/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 IBM SPSS Modeler installation and versionLocate the IBM SPSS Modeler installation directory and check the version information, typically found in product metadata files, registry entries, or the program's about dialogAffected if The installed version matches one of the following: 14.0.0.0, 14.0.0.1, 14.0.0.2, 14.1.0.0, 14.1.0.1, 14.1.0.2, 14.2.0.0, 14.2.0.1, 14.2.0.2, 14.2.0.3, 15.0.0.0, or 15.0.0.1
-
Determine if XML import or parsing features are in useReview workflows, scripts, or user activities that involve loading or importing XML files into IBM SPSS ModelerAffected if Users import, load, or process XML files through Modeler streams or automation scripts
-
Check XML parser configurationExamine Modeler configuration files or settings related to XML parsing to determine if external entity processing is enabledAffected if The XML parser configuration allows external entity resolution or does not explicitly disable XXE processing
-
Inspect recent XML file submissionsReview access logs, stream histories, or import records for XML files that may have been processed by ModelerAffected if XML files from untrusted sources have been parsed by the application
You are affected if IBM SPSS Modeler version 14.0.0.0 through 15.0.0.1 is installed and XML files are being processed by the application, as the XML parser in these versions supports external entity processing.
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 dataApply IBM SPSS Modeler Fix Pack 3 for version 14.2 or Fix Pack 2 for version 15.0, or later patched versions, to disable external entity processing in the XML parser.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5769 — 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-5769 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