CVE-2009-3960: Unspecified vulnerability in BlazeDS 3.2 and earlier, as used in LiveCycle 8.0.1, 8.2.1, and 9.0, LiveCycle...
Unspecified vulnerability in BlazeDS 3.2 and earlier, as used in LiveCycle 8.0.1, 8.2.1, and 9.0, LiveCycle Data Services 2.5.1, 2.6.1, and 3.0, Flex Data Services 2.0.1, and ColdFusion 7.0.2, 8.0, 8.0.1, and 9.0, allows remote attackers to obtain sensitive information via vectors that are associated with a request, and related to injected tags and external entity references in XML documents.
Security readout for executives and security teams
Plain-English summary
This flaw can expose sensitive information when vulnerable Adobe server products process a malicious XML-related request. Although its supplied CVSS score is 6.5, CISA lists it as known exploited, increasing operational urgency for any remaining legacy deployment.
Executive priority
Treat confirmed affected deployments as high priority because exploitation is documented and confidentiality impact is high. Immediately identify exposed legacy systems, reduce access, and assign an owner and deadline for vendor-supported remediation or retirement.
Technical view
CVE-2009-3960 affects BlazeDS 3.2 and earlier as embedded in specified LiveCycle, LiveCycle Data Services, Flex Data Services, and ColdFusion versions. Injected XML tags and external entity references associated with a request can cause sensitive-information disclosure. The supplied vector indicates network access, low complexity, no privileges, user interaction, and high confidentiality impact.
Likely exposure
Exposure is most likely in internet- or partner-accessible applications using the named legacy Adobe versions and processing affected requests. The bundle does not establish whether later versions, custom configurations, or specific endpoints are vulnerable.
Exploitation context
CISA KEV inclusion supports known exploitation. An Exploit-DB entry also exists, indicating public exploit information, but the bundle does not establish current campaign scale, targeted organizations, or exploit reliability.
Researcher notes
The public description is nonspecific but associates disclosure with injected tags and XML external entities. No CWE, affected endpoint, patch, or named mitigation appears in the bundle. Avoid assuming every BlazeDS-integrated route is exploitable; validate exact versions, request paths, XML processing, reachability, and observed behavior.
Mitigation direction
Inventory systems for BlazeDS and the specifically listed Adobe product versions.
Prioritize externally reachable or sensitive-data systems for immediate containment and remediation.
Check current Adobe guidance for supported upgrades, patches, or product-specific mitigations.
Restrict untrusted access to affected services until remediation is validated.
Retire unsupported legacy deployments where a supported remediation path is unavailable.
Validation and detection
Confirm product, embedded BlazeDS, and deployed component versions using authoritative inventory evidence.
Map affected request handlers and determine whether untrusted users can reach them.
Review application, proxy, and security logs for suspicious XML-related requests or unusual outbound retrievals.
Verify remediation against Adobe guidance and repeat version and reachability checks.
Preserve relevant evidence and investigate possible disclosure if suspicious activity is identified.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2009-3960 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.