[KEV] Vulnerability in Adobe BlazeDS (CVE-2009-3960)
Summary
Vulnerability in Adobe BlazeDS (CVE-2009-3960). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited.
Original description
The description as published by the source.
Adobe BlazeDS, which is utilized in LifeCycle and Coldfusion, contains a vulnerability that allows for information disclosure.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2009-3960 has been found in Adobe BlazeDS.
Confidential information can be exposed externally. CVSS score: 6.5/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Adobe BlazeDS CVE-2009-3960" on the vendor's site.
CVE-2009-3960 (Adobe BlazeDS) — CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in Adobe BlazeDS.
Check the vendor advisory for the affected versions of Adobe BlazeDS.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'BlazeDS' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'BlazeDS' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
BlazeDSを grep し、稼働しているサービス・バージョンを把握する。 -
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory NVD
- advisory securitytracker.com
- advisory securityfocus.com
- exploit exploit-db.com
- patch adobe.com
- web secunia.com
- web osvdb.org
- web cisa.gov