CVE-2021-23858
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 · uneditedInformation disclosure: The main configuration, including users and their hashed passwords, is exposed by an unprotected web server resource and can be accessed without authentication. Additionally, device details are exposed which include the serial number and the firmware version by another unprotected web server resource.
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 confidenceCVE-2021-23858 is an unauthenticated information disclosure vulnerability affecting embedded network devices. The flaw exposes the main configuration file (including user credentials with hashed passwords) through an unprotected web server endpoint, allowing remote attackers to harvest authentication material without any credentials. A second unprotected endpoint exposes device metadata including serial numbers and firmware versions, which aids reconnaissance for further attacks.
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<= 12<= 12<= 12<= 12<= 12<= 12<= 12<= 12CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify the device modelVerify the device is a Bosch Rexroth Indramotion Mlc series controller (L20, L40, L25, L45, L65, L85, Xm21, or Xm22) by checking the device label, management interface, or system information page.Affected if The device is one of the listed affected models.
-
Determine the firmware versionAccess the device management interface or use the appropriate command or configuration page to retrieve the installed firmware version. Compare it to the affected range: version 12 or earlier.Affected if The firmware version is 12 or lower.
-
Confirm the web server is accessibleAttempt to access the device web interface over HTTP/HTTPS from a network location. Verify the web server is running and responding to requests without authentication.Affected if The web interface is reachable without providing credentials.
-
Check for unprotected configuration endpointInspect web traffic or attempt to access common configuration file endpoints on the device web server. Look for a response that includes the main configuration file with user credential hashes without requiring authentication.Affected if The configuration file containing user credentials is accessible without authentication.
-
Check for unprotected metadata endpointInspect web traffic or enumerate endpoints that return device metadata. Look for responses exposing serial numbers and firmware versions without authentication.Affected if Device serial numbers and firmware versions are exposed without authentication.
The environment is affected if the device is a Bosch Rexroth Indramotion Mlc (L20, L40, L25, L45, L65, L85, Xm21, or Xm22) running firmware version 12 or lower, and the web interface with unprotected endpoints is exposed 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 dataRestrict access to the vulnerable web server resources by implementing proper authentication and session management. Additionally, apply any available vendor patches and consider network segmentation to limit exposure of administrative interfaces.
- 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-2021-23858 — 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-2021-23858 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