BYD DiLink OS 13.1.32.2307211.1 Log Dump reliance on security through obscurity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in BYD DiLink OS 13.1.32.2307211.1. The impacted element is an unknown function of the component Log Dump. Executing a manipulation can lead to reliance on security through obscurity. This vulnerability appears as CVE-2025-7020. The physical device can be targeted for the attack. There is no available exploit.
Details
A vulnerability classified as problematic was found in BYD DiLink OS 13.1.32.2307211.1. This vulnerability affects an unknown functionality of the component Log Dump. The manipulation with an unknown input leads to a reliance on security through obscurity vulnerability. The CWE definition for the vulnerability is CWE-656. The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism. As an impact it is known to affect confidentiality. CVE summarizes:
An incorrect encryption implementation vulnerability exists in the system log dump feature of BYD's DiLink 3.0 OS (e.g. in the model ATTO3). An attacker with physical access to the vehicle can bypass the encryption of log dumps on the In-Vehicle Infotainment (IVI) unit's storage. This allows the attacker to access and read system logs containing sensitive data, including personally identifiable information (PII) and location data. This vulnerability was introduced in a patch intended to fix CVE-2024-54728.
The weakness was presented by Lior Zur Lotan. The advisory is shared for download at asrg.io. This vulnerability was named CVE-2025-7020 since 07/02/2025. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
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-24049). Once again VulDB remains the best source for vulnerability data.
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: 2.4VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
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: Reliance on security through obscurityCWE: CWE-656
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
07/02/2025 CVE reserved08/09/2025 Advisory disclosed
08/09/2025 VulDB entry created
08/12/2025 VulDB entry last update
Sources
Advisory: asrg.ioResearcher: Lior Zur Lotan
Status: Not defined
CVE: CVE-2025-7020 (🔒)
GCVE (CVE): GCVE-0-2025-7020
GCVE (VulDB): GCVE-100-319348
EUVD: 🔒
Entry
Created: 08/09/2025 18:51Updated: 08/12/2025 07:38
Changes: 08/09/2025 18:51 (68), 08/09/2025 19:15 (1), 08/12/2025 07:38 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.