CVE-2025-25737

6.8 MEDIUM

📋 TL;DR

This vulnerability allows attackers to bypass authentication on Kapsch TrafficCom RIS-9160 and RIS-9260 Roadside Units via brute-force attacks due to weak BIOS password requirements. Organizations using these specific RSU versions in traffic management systems are affected. Attackers could gain unauthorized access to device BIOS settings.

💻 Affected Systems

Products:
  • Kapsch TrafficCom RIS-9160
  • Kapsch TrafficCom RIS-9260
Versions: v3.2.0.829.23, v3.8.0.1119.42, v4.6.0.1211.28
Operating Systems: Embedded firmware
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of specified versions are vulnerable due to insufficient password complexity requirements.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers gain full BIOS control, potentially disabling security features, installing persistent malware, or bricking devices, disrupting traffic management systems.

🟠

Likely Case

Attackers gain unauthorized BIOS access to modify boot settings, disable security features, or extract sensitive system information.

🟢

If Mitigated

With strong password policies and network segmentation, impact is limited to isolated devices with minimal operational disruption.

🌐 Internet-Facing: MEDIUM - RSUs are typically deployed roadside but may have limited direct internet exposure; risk depends on network architecture.
🏢 Internal Only: HIGH - If attackers gain physical or network access to RSUs, they can exploit this vulnerability to compromise device integrity.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires physical or network access to RSU BIOS interface; brute-force tools needed but widely available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Kapsch for updated firmware versions addressing CVE-2025-25737

Vendor Advisory: https://www.kapsch.net/en

Restart Required: No

Instructions:

1. Contact Kapsch support for patched firmware. 2. Backup current configuration. 3. Apply firmware update via management interface. 4. Verify BIOS password requirements are enforced.

🔧 Temporary Workarounds

Enforce Strong BIOS Passwords

all

Manually configure complex passwords for Supervisor and User BIOS accounts exceeding minimum length and complexity requirements.

Access BIOS setup during boot > Security settings > Set strong passwords for all accounts

🧯 If You Can't Patch

  • Implement network segmentation to isolate RSUs from untrusted networks
  • Enable physical security controls and monitor for unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check device firmware version via web interface or console; if matches affected versions and BIOS passwords are weak/short, device is vulnerable.

Check Version:

Login to RSU management interface and check System Information or Firmware Version section

Verify Fix Applied:

Verify firmware version is updated beyond affected versions and test that BIOS rejects weak passwords during setup.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed BIOS login attempts
  • BIOS configuration changes outside maintenance windows

Network Indicators:

  • Unusual traffic to RSU management interfaces
  • Brute-force patterns to BIOS access ports

SIEM Query:

source="rsu_logs" AND (event="authentication_failed" AND count>10) OR event="bios_config_change"

🔗 References

📤 Share & Export