Kapsch TrafficCom RIS-9160/TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28 EEPROM access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Kapsch TrafficCom RIS-9160 and TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component EEPROM. The manipulation leads to access control. This vulnerability is documented as CVE-2025-25732. It is possible to launch the attack on the physical device. There is not any exploit available.
Details
A vulnerability was found in Kapsch TrafficCom RIS-9160 and TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28 and classified as critical. This issue affects an unknown code block of the component EEPROM. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Incorrect access control in the EEPROM component of Kapsch TrafficCom RIS-9160 & RIS-9260 Roadside Units (RSUs) v3.2.0.829.23, v3.8.0.1119.42, and v4.6.0.1211.28 allows attackers to replace password hashes stored in the EEPROM with hashes of their own, leading to the escalation of privileges to root.
The identification of this vulnerability is CVE-2025-25732 since 02/07/2025. The exploitation is known to be difficult. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.4
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/07/2025 CVE reserved08/26/2025 Advisory disclosed
08/26/2025 VulDB entry created
08/29/2025 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2025-25732 (🔒)
GCVE (CVE): GCVE-0-2025-25732
GCVE (VulDB): GCVE-100-321431
Entry
Created: 08/26/2025 17:13Updated: 08/29/2025 19:32
Changes: 08/26/2025 17:13 (52), 08/29/2025 19:32 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.