CVE-2014-3066
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 Tivoli Endpoint Manager 9.1 before 9.1.1088.0 allows remote attackers to read arbitrary files via XML data containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.
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 Tivoli Endpoint Manager versions 9.1 before 9.1.1088.0 contains an XML External Entity (XXE) injection vulnerability. Remote unauthenticated attackers can exploit this by submitting XML data with malicious external entity declarations that reference local file paths, allowing arbitrary file disclosure from the server's file system.
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= 9.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 the installed version of IBM Tivoli Endpoint ManagerLocate the version information through the Tivoli Endpoint Manager console, or check the BES Server/Relay version via the management interface or installed software listingAffected if The version is 9.1.x and is earlier than 9.1.1088.0 (including any 9.1 release before that threshold)
-
Confirm the BES Server or BES Relay component is runningCheck if the BES Server or BES Relay service is active and listening on its management port, as this component handles XML-based client communicationsAffected if The BES Server/Relay service is exposed and accessible to network clients, enabling XML submission endpoints
-
Determine if external XML input is acceptedReview the web service endpoints or API configurations exposed by the BES Server for XML-handling capabilitiesAffected if The server accepts XML submissions from remote clients without requiring authentication or has unprotected XML parsing endpoints
-
Verify the XML parser configurationExamine the XML parser settings on the BES Server to determine if external entity processing is enabled or disabledAffected if External entity processing is enabled in the XML parser configuration, allowing XXE exploitation
You are affected if your IBM Tivoli Endpoint Manager version is 9.1.x and is earlier than 9.1.1088.0, and the BES Server/Relay component that handles XML input is accessible to remote clients.
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 IBM Tivoli Endpoint Manager to version 9.1.1088.0 or later, which includes a patch that disables external entity processing in the XML parser to prevent XXE attacks.
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3066 — 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-2014-3066 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