CVE-2021-23843
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 · uneditedThe Bosch software tools AccessIPConfig.exe and AmcIpConfig.exe are used to configure certains settings in AMC2 devices. The tool allows putting a password protection on configured devices to restrict access to the configuration of an AMC2. An attacker can circumvent this protection and make unauthorized changes to configuration data on the device. An attacker can exploit this vulnerability to manipulate the device\'s configuration or make it unresponsive in the local network. The attacker needs to have access to the local network, typically even the same subnet.
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 confidenceThe AccessIPConfig.exe and AmcIpConfig.exe tools used to configure Bosch AMC2 devices contain a password protection bypass vulnerability. An attacker with local network access (typically same subnet) can circumvent the authentication mechanism and make unauthorized changes to device configuration, potentially rendering the device unresponsive.
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 dataall versions= 3.0<= 3.8.0< 4.9.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bosch AMC2 firmware versionAccess the AMC2 device admin interface or check firmware via device management console. Look for firmware version information in system status or device properties.Affected if Firmware version is any version (all versions affected)
-
Check Bosch Access Management System versionOpen the Access Management System application, navigate to About or System Information section to view the installed software version.Affected if Version equals 3.0 exactly
-
Check Bosch Access Professional Edition versionLaunch Access Professional Edition, go to Help > About or check the software version through the control panel add/remove programs.Affected if Version is 3.8.0 or lower
-
Check Bosch Building Integration System versionOpen Building Integration System, locate System Information or About menu to identify the installed software version.Affected if Version is lower than 4.9.1
-
Locate AccessIPConfig.exe or AmcIpConfig.exe toolsSearch the system for these configuration tools using file explorer or command: dir /s C:\AccessIPConfig.exe or dir /s C:\AmcIpConfig.exe. Also check default installation paths under Bosch program directories.Affected if Either tool is present on the system
-
Verify network exposure of AMC2 devicesCheck network configuration of AMC2 devices to determine if they are accessible from the local subnet without proper network segmentation or access controls.Affected if Device is reachable from local subnet without network-based access restrictions
A system is affected if it runs any of the listed product versions AND has AMC2 configuration tools accessible on the network, allowing an attacker on the same subnet to bypass authentication.
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 data4.9.1
Restrict network access to AMC2 devices and configuration tools using network segmentation and access control lists. Monitor for unauthorized configuration changes and apply vendor patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23843 — 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-23843 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