CVE-2025-41657VulnerabilityPublished 10 Jun 2025

CVE-2025-41657: Auma AC1.2 · Observable Behavioral Discrepancy With Equivalent Products

Affects Auma AC1.2Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Auma AC1.2	Affected =01.01.2024	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first conduct an inventory of all Auma AC1.2 devices deployed within the affected delivery window (01.01.2024 to 09.05.2025). Network segmentation and physical security controls should be enhanced to restrict unauthorized physical proximity to these devices, limiting Bluetooth signal exposure. Disabling Bluetooth functionality on the devices, if configurable, should be prioritized to eliminate the attack vector. If disabling is not possible, organizations should monitor for unusual Bluetooth scanning activity in the vicinity of critical assets. Additionally, organizations should engage with Auma for official guidance and request firmware updates or patches that disable or secure the undocumented Bluetooth stack. Incorporating Bluetooth signal detection tools into security monitoring can help detect potential fingerprinting attempts. Finally, raising awareness among operational technology (OT) and security teams about this vulnerability will ensure timely response and risk management.

Description

Due to an undocumented active bluetooth stack on products delivered within the period 01.01.2024 to 09.05.2025 fingerprinting is possible by an unauthenticated adjacent attacker.

Impact

For European organizations using Auma AC1.2 devices, particularly in industrial or critical infrastructure environments where these products are deployed, this vulnerability poses a risk primarily related to information disclosure. An attacker could perform reconnaissance to identify specific devices and their deployment locations, which may facilitate targeted attacks or espionage. While the vulnerability does not directly allow device control or disruption, the fingerprinting capability can aid adversaries in mapping networked assets and planning more sophisticated attacks. This is especially relevant for sectors such as energy, manufacturing, and utilities where Auma products are commonly used for automation and control. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing risk in environments with physical access by unauthorized personnel or where Bluetooth signals can be intercepted from adjacent areas. However, the medium severity and limited impact suggest that the immediate threat is moderate, but it should not be ignored given the strategic importance of affected systems.

CWE-207Observable Behavioral Discrepancy With Equivalent Products (opens in a new tab)
Variant weakness
The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is observable to an attacker.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

certvde.com/en/advisories/VDE-2025-047 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 01:02 UTC

WeaknessesCWE-207

Technical details

References

Community reviews