Ak Sm 800a FirmwareOperating system · Danfoss

CVE-2023-25914

HIGH · 8.8 CVSS v3.1 Published 2023-08-21
Fix available
A fix is available. Upgrade to after 3.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Due to improper restriction, authenticated attackers could retrieve and read system files of the underlying server through the XML interface. The information that can be read can lead to a full system compromise.

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 confidence

This is an authenticated local file inclusion (LFI) vulnerability in an XML interface where improper input validation allows authenticated attackers to read arbitrary system files from the underlying server. The flaw enables retrieval of sensitive configuration files, credentials, or other system files that could be chained to achieve full system compromise.

MitigationImplement strict input validation and disable external entity processing in the XML parser; restrict the XML interface to prevent path traversal and limit file system access to authorized paths only.

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
Ak Sm 800a FirmwareOperating system
Affected:<= 3.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check firmware version
    Access the Danfoss Ak Sm 800a web interface or system information page and locate the firmware version number. This is typically found under 'System', 'About', or 'Status' sections in the management console.
    Affected if The firmware version is 3.3 or lower.
  2. Verify XML interface accessibility
    Attempt to access the XML interface endpoint on the device. This is usually found at a path like '/xml' or '/api/xml' on the management web server. Confirm whether the endpoint responds to requests.
    Affected if The XML interface endpoint is accessible and responds without errors.
  3. Confirm authentication is enforced on XML interface
    Examine the authentication configuration for the XML interface. Check if the interface requires valid credentials or session tokens before allowing access to any functionality.
    Affected if The XML interface allows access without proper authentication or accepts any credentials without validation.
  4. Test for path traversal protection
    Send a crafted XML request to the interface with path traversal sequences (such as ../../../etc/passwd or ../../../windows/win.ini) in file path parameters. Observe whether the server returns the contents of arbitrary files or blocks the request.
    Affected if The server returns contents of files outside the intended directory or responds with file data rather than an access denied error.

The environment is affected if the Danfoss Ak Sm 800a firmware is version 3.3 or lower AND the XML interface is accessible with authentication that can be bypassed or is improperly validated, allowing path traversal to read arbitrary system files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 3.3
Interim mitigation

Implement strict input validation and disable external entity processing in the XML parser; restrict the XML interface to prevent path traversal and limit file system access to authorized paths only.

Fix this in Ak Sm 800a Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25914 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25914 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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