Kapsch TrafficCom RIS-9160/TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28 SPI Protected Range Register security-sensitive hardware controls with missing lock bit protection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $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 rated as problematic. This affects an unknown part of the component SPI Protected Range Register Handler. This manipulation causes Local Privilege Escalation. This vulnerability appears as CVE-2025-25735. The attack requires local access. There is no available exploit.
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. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component SPI Protected Range Register Handler. The manipulation with an unknown input leads to a local privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-1233. The product uses a register lock bit protection mechanism, but it does not ensure that the lock bit prevents modification of system registers or controls that perform changes to important hardware system configuration. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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 were discovered to lack SPI Protected Range Registers (PRRs), allowing attackers with software running on the system to modify SPI flash in real-time.
This vulnerability is known as CVE-2025-25735 since 02/07/2025. The exploitation appears to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-25797). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.5
VulDB Temp Score: 4.5
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: Security-sensitive hardware controls with missing lock bit protectionCWE: CWE-1233
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
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/27/2025 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2025-25735 (🔒)
GCVE (CVE): GCVE-0-2025-25735
GCVE (VulDB): GCVE-100-321433
EUVD: 🔒
Entry
Created: 08/26/2025 17:14Updated: 08/27/2025 16:25
Changes: 08/26/2025 17:14 (50), 08/26/2025 18:59 (1), 08/27/2025 16:25 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.