CVE-2022-31807
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 · uneditedA vulnerability has been identified in Building X - Security Manager Edge Controller (ACC-AP) (All versions). Affected devices do not properly check the integrity of firmware updates. This could allow a local attacker to upload a maliciously modified firmware onto the device. In a second scenario, a remote attacker who is able to intercept the transfer of a valid firmware from the server to the device could modify the firmware "on the fly".
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 Building X Security Manager Edge Controller (ACC-AP) fails to verify the integrity of firmware updates before installation. Affected devices lack cryptographic signature validation or checksum verification, allowing an attacker with local access to flash malicious firmware, or a remote attacker performing a man-in-the-middle attack to modify firmware in transit.
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 versionsall versionsCVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 modelAccess the device management interface or check the physical device label for the model number. Look for ACC-AP, AC5102, or Sipass Integrated identifiers.Affected if The device model is Siemens Sipass Integrated ACC-AP or AC5102 (acc G2)
-
Check the installed firmware versionLog into the device admin panel or use the firmware management interface to view the currently installed firmware version.Affected if Any firmware version is installed on the affected device models (all versions are vulnerable)
-
Verify if firmware signature validation existsAccess the firmware update settings or security configuration menu. Look for options labeled 'Verify firmware signature', 'Validate checksum', 'Check firmware integrity', or 'Secure boot'.Affected if No signature verification, checksum validation, or integrity check options are found in the firmware update settings (the vulnerability exists when these are absent)
-
Inspect the firmware update mechanismCheck the firmware distribution configuration or network settings for the update process. Look for TLS/SSL settings or secure channel configuration.Affected if Firmware updates are delivered over unencrypted channels or no TLS enforcement is configured for firmware distribution
You are affected if you have a Siemens Sipass Integrated ACC-AP or AC5102 device and the firmware update settings show no signature verification, checksum validation, or secure boot mechanisms are implemented.
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 cryptographic signature verification for all firmware updates using asymmetric keys and secure boot chain validation. Additionally, enforce TLS for all firmware distribution to prevent remote interception and modification.
- Consultation12.0 h
- Implementation60.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $30,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31807 — 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-31807 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