Stack buffer overflow in method bac-deviceobject
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.5%
exploitation probability
0.5%top 63% of all CVEs
observed exploitation
nono source reports it
In short
A flaw in the bac-deviceobject method allows someone with user access to overflow a memory buffer on the stack, potentially taking complete control of the system as root. This is dangerous because it can lead to full system compromise.
Technical detail
A stack buffer overflow exists in the bac-deviceobject method (CWE-121) that can be triggered by a remote attacker with user-level privileges. Exploitation allows arbitrary code execution with root privileges, bypassing normal access controls and enabling complete system takeover.
Summary generated and translated by AI from the official description.
A remote attacker with user privileges can exploit a stack buffer overflow to gain full system access as root.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
MBS · Double-A ProfibusMBS · Double-A x-linkMBS · Double-X CANMBS · Double-X DALIMBS · Double-X KNXMBS · Double-X LONMBS · Double-X M-BusMBS · Double-X PROFINETMBS · Double-X x-linkMBS · Single-AMBS · Single-XMBS · Triple-X KNX+DALIMBS · Triple-X KNX+LONMBS · Triple-X KNX+M-BusMBS · Triple-X PROFINET+DALIMBS · Triple-X PROFINET+KNXMBS · Triple-X PROFINET+LONMBS · Triple-X PROFINET+M-Bus