CVE-2024-52285
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 SiPass integrated AC5102 (ACC-G2) (All versions < V6.4.8), SiPass integrated ACC-AP (All versions < V6.4.8). Affected devices expose several MQTT URLs without authentication. This could allow an unauthenticated remote attacker to access sensitive data.
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 confidenceSiPass integrated AC5102 (ACC-G2) and ACC-AP access control devices running firmware versions prior to V6.4.8 expose MQTT service URLs without authentication. An unauthenticated remote attacker could access these endpoints to retrieve sensitive access control data transmitted over the MQTT protocol.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 SiPass access control devices on the networkScan the network for SiPass integrated AC5102 (ACC-G2) or ACC-AP devices. Check device inventory or use network discovery to locate these specific models.Affected if Any SiPass integrated AC5102 or ACC-AP devices are found in the environment
-
Determine firmware version of SiPass devicesAccess the device management interface or use the vendor-provided diagnostic tool to retrieve the current firmware version. Compare against the affected range (versions prior to V6.4.8).Affected if Firmware version is lower than V6.4.8 (e.g., V6.4.7, V6.4.6, etc.)
-
Verify if MQTT service is enabledCheck the device configuration settings or documentation to determine whether the MQTT protocol interface has been enabled on the device.Affected if MQTT service is enabled on the device
-
Check MQTT network exposureTest network connectivity to common MQTT ports (default 1883/8883) on the SiPass device from an unauthenticated perspective to see if endpoints are reachable without credentials.Affected if MQTT ports are accessible from the network without authentication being required
A user is affected if they have SiPass integrated AC5102 or ACC-AP devices running firmware versions prior to V6.4.8 with MQTT service enabled and exposed without 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.
dbcve · scopedUpgrade SiPass integrated AC5102 and ACC-AP devices to firmware version V6.4.8 or later to patch the authentication bypass in the MQTT interface.
V6.4.8
- Obtain the V6.4.8 firmware update from the official Siemens cert-portal or Siemens Product Security website
- Review the firmware upgrade instructions specific to your SiPass integrated AC5102 (ACC-G2) or ACC-AP device
- Apply the firmware update following the manufacturer's documented upgrade procedure
- After upgrading, verify that the MQTT endpoints now require authentication
- Confirm the device is running version V6.4.8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2024-52285 — 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-2024-52285 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