End-of-Train/Head-of-Train BCH weak authentication

Summaryinfo

A vulnerability has been found in End-of-Train and Head-of-Train and classified as very critical. Affected by this issue is some unknown functionality of the component BCH Handler. Performing a manipulation results in weak authentication. This vulnerability was named CVE-2025-1727. The attack needs to be approached within the local network. There is no available exploit.

Detailsinfo

A vulnerability classified as very critical has been found in End-of-Train and Head-of-Train (the affected version unknown). This affects an unknown part of the component BCH Handler. The manipulation with an unknown input leads to a weak authentication vulnerability. CWE is classifying the issue as CWE-1390. The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The protocol used for remote linking over RF for End-of-Train and Head-of-Train (also known as a FRED) relies on a BCH checksum for packet creation. It is possible to create these EoT and HoT packets with a software defined radio and issue brake control commands to the EoT device, disrupting operations or potentially overwhelming the brake systems.

The weakness was presented by Neil Smith and Eric Reuter as icsa-25-191-10. The advisory is shared at cisa.gov. This vulnerability is uniquely identified as CVE-2025-1727 since 02/26/2025. The exploitability is told to be easy. The attack needs to be done within the local network. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/11/2025).

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-21087). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• End-of-Train
• Head-of-Train

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion