Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-42344 high CVSS 7.3

XXE (XML External Entity) in org.opencms:opencms-core (CVE-2023-42344)

Summary

Vulnerability in org.opencms:opencms-core (CVE-2023-42344). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.5.1 or later.

Original description

The description as published by the source.

Alkacon OpenCms before 10.5.1 allows remote unauthenticated attackers to obtain sensitive information via a cmis-online/query XXE attack on a Chemistry servlet.

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 vulnerability tracked as CVE-2023-42344 has been found in org.opencms:opencms-core.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: upgrade org.opencms:opencms-core to 10.5.1 or later.
If unsure, ask your IT team or search "org.opencms:opencms-core CVE-2023-42344" on the vendor's site.

CVE-2023-42344 (org.opencms:opencms-core) — CWE-611 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 10.5.1 — apply immediately
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.

❓ What is the problem

A vulnerability (CWE-611) exists in org.opencms:opencms-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.opencms:opencms-core.

🔥 Severity

Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.5.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.opencms:opencms-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.opencms:opencms-core to 10.5.1

    ステージング環境で 10.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.opencms:opencms-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.5.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details