XXE (XML External Entity) in org.opencms:opencms-core (CVE-2023-42346)
Summary
Vulnerability in org.opencms:opencms-core (CVE-2023-42346). Confidential information can be exposed externally. Mitigation: upgrade to 16.0 or later.
Original description
The description as published by the source.
Alkacon OpenCms before 16 allows XXE when the <!DOCTYPE> refers to an external host.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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 weakness called CVE-2023-42346 was discovered in org.opencms:opencms-core.
Severity is High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "org.opencms:opencms-core CVE-2023-42346".
CVE-2023-42346 (org.opencms:opencms-core). Severity: High / CVSSv3 7.5. Category: CWE-611.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2023-42346) in org.opencms:opencms-core. A serious software flaw has been identified.
Target versions of org.opencms:opencms-core (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-611)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web cve@mitre.org
- web labs.watchtowr.com
- web github.com