CVE-2022-47648
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 · uneditedAn Improper Access Control vulnerability allows an attacker to access the control panel of the B420 without requiring any sort of authorization or authentication due to the IP based authorization. If an authorized user has accessed a publicly available B420 product using valid credentials, an insider attacker can gain access to the same panel without requiring any sort of authorization. The B420 module was already obsolete at the time this vulnerability was found (The End of Life announcement was made in 2013).
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 B420 module has an improper access control vulnerability where IP-based authorization is used instead of proper authentication. An attacker on the same network or with access to a publicly exposed B420 device can access the control panel without any credentials, bypassing all authorization checks.
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= 02.02.0001CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 Bosch B420 devices on the networkScan network for devices responding to HTTP/HTTPS on typical Bosch device ports (typically port 80/443 or vendor-specific ports). Check device web interface for 'B420' model identifier in the header or device information page.Affected if A Bosch B420 device is found on the network with its web control panel accessible.
-
Confirm firmware version is 02.02.0001Access the B420 device web interface and navigate to the firmware/version information page, or use SNMP/CLI if available to query the firmware build number.Affected if The installed firmware version is exactly 02.02.0001.
-
Verify network exposure of the control panelCheck firewall rules, NAT configurations, or ACLs that allow access to the B420 device IP from outside the trusted internal network. Test access by attempting to reach the device from an untrusted network segment.Affected if The B420 control panel is reachable from networks other than a strictly isolated management VLAN.
-
Test for unauthenticated accessAttempt to access the B420 control panel URL (such as / or /login) directly via HTTP/HTTPS without providing any username or password. Observe if the dashboard or configuration pages load without authentication.Affected if The control panel loads or presents any functional interface without requiring credentials.
A user is affected if a Bosch B420 device running firmware 02.02.0001 has its control panel accessible over the network without authentication, allowing any attacker on the same network to bypass authorization entirely.
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 dataSince the B420 is obsolete (EOL since 2013) with no vendor patch available, immediately isolate the device from public networks via firewall/ACLs, implement proper network segmentation, or replace with a supported device.
- Consultation6.0 h
- Implementation12.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 $6,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47648 — 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-2022-47648 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