ISO 15118-2 Network and Application Protocol Requirements communication channel to intended endpoints
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in ISO 15118-2 Network and Application Protocol Requirements 8.3. The affected element is an unknown function of the component Signal Level Attenuation Characterization Protocol Handler. Performing a manipulation results in communication channel to intended endpoints. This vulnerability is known as CVE-2025-12357. Access to the local network is required for this attack. No exploit is available. It is advisable to enhance encryption further.
Details
A vulnerability was found in ISO 15118-2 Network and Application Protocol Requirements 8.3. It has been classified as critical. This affects an unknown functionality of the component Signal Level Attenuation Characterization Protocol Handler. The manipulation with an unknown input leads to a communication channel to intended endpoints vulnerability. CWE is classifying the issue as CWE-923. The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
By manipulating the Signal Level Attenuation Characterization (SLAC) protocol with spoofed measurements, an attacker can stage a man-in-the-middle attack between an electric vehicle and chargers that comply with the ISO 15118-2 part. This vulnerability may be exploitable wirelessly, within close proximity, via electromagnetic induction.
The advisory is shared at cisa.gov. This vulnerability is uniquely identified as CVE-2025-12357. The exploitability is told to be easy. The attack can only be done within the local network. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The best possible mitigation is suggested to be adding encryption.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-37371). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA Vector: 🔒
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: Communication channel to intended endpointsCWE: CWE-923
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
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: EncryptionStatus: 🔍
0-Day Time: 🔒
Timeline
10/31/2025 Advisory disclosed10/31/2025 VulDB entry created
03/17/2026 VulDB entry last update
Sources
Advisory: icsa-25-303-01Status: Confirmed
CVE: CVE-2025-12357 (🔒)
GCVE (CVE): GCVE-0-2025-12357
GCVE (VulDB): GCVE-100-330765
EUVD: 🔒
Entry
Created: 10/31/2025 11:01Updated: 03/17/2026 20:06
Changes: 10/31/2025 11:01 (51), 10/31/2025 17:26 (24), 10/31/2025 17:48 (1), 03/17/2026 20:06 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.