CVE-2023-24470
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 · uneditedPotential XML External Entity Injection in ArcSight Logger versions prior to 7.3.0.
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 · moderate confidenceThis is an XML External Entity (XXE) injection vulnerability in ArcSight Logger, a security logging and compliance product. The vulnerability allows attackers to inject malicious XML that can reference external entities, potentially leading to disclosure of local files, Server-Side Request Forgery (SSRF), or denial of service. The flaw exists in versions prior to 7.3.0 due to insecure XML parser configuration.
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< 7.3.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
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.
-
Confirm ArcSight Logger installationLocate the ArcSight Logger installation directory. Common paths include /opt/arcsight/logger on Linux or C:\Program Files\ArcSight\Logger on Windows. Check for the logger product files or running processes named 'arcsight' or 'logger'.Affected if ArcSight Logger is present on the system and the version is below 7.3.0
-
Determine installed versionRun the version command from the installation bin directory, such as 'arcsight logger version' or check the web interface About page. Alternatively, locate a version.info or version.txt file in the installation directory.Affected if The installed version is any release prior to 7.3.0 (for example 7.0.x, 7.1.x, 7.2.x)
-
Identify XML input sourcesReview the logger configuration for connectors, parsers, or integration points that accept XML-based inputs. Check for syslog connectors, CEF format parsers, or custom XML event sources configured within the Logger.Affected if XML-based inputs are being processed by the Logger and the version is below 7.3.0
-
Check XML parser settingsExamine XML parser configuration files within the Logger installation for settings related to external entity processing, DOCTYPE handling, or XXE protection. Look in configuration directories for XML parser or transformer settings.Affected if External entity processing is enabled or not explicitly disabled in the XML parser configuration, and the Logger version is below 7.3.0
The environment is affected if Micro Focus ArcSight Logger is installed with any version below 7.3.0 and processes XML-based inputs with external entity processing allowed in the parser configuration.
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.
dbcve · scoped7.3.0
Upgrade ArcSight Logger to version 7.3.0 or later, which contains the fix for this vulnerability. If immediate upgrade is not feasible, consider disabling external entity processing in XML parsers and implementing input validation for XML-based inputs.
7.3.0
- Back up all ArcSight Logger configurations, data, and certificates before starting the upgrade
- Download the ArcSight Logger 7.3.0 upgrade package from the Micro Focus support portal
- Review the official Micro Focus upgrade documentation for upgrading from your current version
- Execute the upgrade following the standard upgrade procedure (typically using the installer or OVA/OVF for your deployment type)
- After upgrade completes, verify the version shows 7.3.0 in the product UI or via CLI command
- Confirm XML parsing functionality is working correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24470 — 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-2023-24470 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