Kapsch TrafficCom RIS-9160/TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28 SPI Flash Chip access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Kapsch TrafficCom RIS-9160 and TrafficCom RIS-9260 3.2.0.829.23/3.8.0.1119.42/4.6.0.1211.28. This vulnerability affects unknown code of the component SPI Flash Chip. Such manipulation leads to access control. This vulnerability is traded as CVE-2025-25733. The attack can be executed directly on the physical device. There is no 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. It has been rated as critical. Affected by this issue is an unknown functionality of the component SPI Flash Chip. 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. CVE summarizes:
Incorrect access control in the SPI Flash Chip 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 physically proximate attackers to arbitrarily modify SPI flash regions, leading to a degradation of the security posture of the device.
This vulnerability is handled as CVE-2025-25733 since 02/07/2025. The exploitation is known to be easy. Local access is required to approach this attack. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.1
VulDB Temp Score: 4.1
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-25733 (🔒)
GCVE (CVE): GCVE-0-2025-25733
GCVE (VulDB): GCVE-100-321434
Entry
Created: 08/26/2025 17:14Updated: 08/29/2025 19:32
Changes: 08/26/2025 17:14 (52), 08/29/2025 19:32 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.