CVE-2022-32535
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 Ethernet switch PRA-ES8P2S with software version 1.01.05 runs its web server with root privilege. In combination with CVE-2022-23534 this could give an attacker root access to the switch.
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 confidenceThe Bosch PRA-ES8P2S Ethernet switch runs its web server with root privileges. When combined with CVE-2022-23534 (an authentication bypass or code injection vulnerability), an attacker can escalate privileges to achieve full root access to the switch, effectively compromising the entire device.
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<= 1.01.05CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/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 the device modelAccess the device's web interface or check the device label/menu for the exact model number to confirm it is a Bosch PRA-ES8P2S Ethernet switchAffected if The device is not a Bosch PRA-ES8P2S switch, then this specific CVE does not apply
-
Check the firmware versionLog into the device's web interface or CLI and navigate to the firmware/version information section to determine the installed firmware versionAffected if The firmware version is at or below 1.01.05, indicating the device is running a vulnerable version
-
Verify the web server is enabledCheck the device configuration settings to confirm the embedded web server interface is enabled and accessibleAffected if The web server is disabled, the privilege escalation vector through the web server is not reachable
-
Confirm remote management accessExamine network configuration to determine if remote web management is accessible from network segments outside the local management VLANAffected if Remote management access is exposed to untrusted networks, enabling the combined attack with CVE-2022-23534 to be exploited
The device is affected if it is a Bosch PRA-ES8P2S switch running firmware version 1.01.05 or lower with the web interface enabled and accessible, particularly from untrusted network segments.
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.
dbcve · scopedApply vendor-supplied firmware updates when available; until then, restrict network access to the management interface using network segmentation or firewall rules, and monitor for unauthorized access attempts.
Firmware version > 1.01.05 (obtain exact fixed version from Bosch PSIRT)
- 1. Identify the current firmware version of the PRA-ES8P2S switch by accessing the web management interface or using the CLI command to display firmware version.
- 2. Navigate to the Bosch Product Security incident response page (psirt.bosch.com) to obtain the recommended firmware version that addresses CVE-2022-32535 and CVE-2022-23534.
- 3. Download the updated firmware file from the official Bosch support portal.
- 4. Create a backup of the current switch configuration before proceeding with the firmware update.
- 5. Access the switch's firmware upgrade function through the web interface or CLI.
- 6. Upload and apply the new firmware version, following the manufacturer's upgrade procedure.
- 7. Verify the upgrade was successful by checking the new firmware version.
- 8. Confirm the web server now runs with non-root privileges after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32535 — 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-32535 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