Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| EVbee | EVbee Service | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Evbee | Evbee Service |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.261% probability within 30 days)
| Link | Providers |
|---|---|
| https://csirt.divd.nl/DIVD-2026-00001/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Evbee
Evbee evbee Service |
|
| Vendors & Products |
Evbee
Evbee evbee Service |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The EVbee Service Android app uses TLS encrypted communication (HTTPS), but does not validate the certificate provided by the server. This allows an attacker on the network path between the app and EVbee server to intercept and manipulate the communication between the app and server. The traffic is weakly encrypted using RC4 with a hardcoded key, which allows an attacker to gain access to the communication. Part of this communication involves access codes to charging stations. This issue affects EVbee Service: v1.4.101.00. | |
| Title | Adversary-in-the-Middle (AitM) attack vulnerability in EVbee Service app | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV4_0
|