CVE-2023-23590
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 · uneditedMercedes-Benz XENTRY Retail Data Storage 7.8.1 allows remote attackers to cause a denial of service (device restart) via an unauthenticated API request. The attacker must be on the same network as the device.
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 · high confidenceMercedes-Benz XENTRY Retail Data Storage 7.8.1 contains an unauthenticated API endpoint that accepts requests without validation. An attacker on the same network as the device can send specially crafted API requests that cause the device to restart, resulting in denial of service. The vulnerability stems from missing authentication requirements on the API interface.
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.8.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify the XENTRY Retail Data Storage firmware versionAccess the device management interface or check system information to determine the installed firmware version. Common methods include logging into the device console, checking the web UI, or retrieving system details via SNMP or vendor-specific management tool.Affected if The installed firmware version is exactly 7.8.1 (no other versions are listed as affected)
-
Confirm the API interface is enabledLocate the API service configuration in the device settings or check running services on the system. Look for references to REST API, web services, or similar interface configurations.Affected if The API interface feature is enabled or exposed on the device
-
Determine if API endpoints require authenticationAttempt to access the API endpoint without credentials or review the API security configuration settings. Check if authentication tokens, API keys, or login sessions are enforced for API requests.Affected if The API endpoints accept requests without requiring authentication (no login, token, or credential validation)
-
Assess network accessibility of the API serviceReview network configuration to determine if the API port is exposed to the network. Check firewall rules, interface bindings, and network segment placement.Affected if The API service is accessible from the network without network-level restrictions
A user is affected only if they have exactly version 7.8.1 of Mercedes-Benz XENTRY Retail Data Storage firmware with the unauthenticated API interface enabled and accessible on the network.
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.
From vendor dataImplement authentication requirements for all API endpoints and apply any vendor-supplied patches or firmware updates. As a compensating control, isolate the device on a restricted network segment with firewall rules to limit API access to authorized personnel and systems only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2023-23590 — 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-23590 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