| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $25k-$100k | 0.00 |
Summary
A vulnerability marked as very critical has been reported in Mazda Model 2015/2016. Impacted is an unknown function. Performing a manipulation results in improper authentication. This vulnerability is identified as CVE-2023-32219. The attack can only be performed from the local network. There is not any exploit available.
Details
A vulnerability classified as very critical has been found in Mazda Model 2015/2016. This affects an unknown code. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A Mazda model (2015-2016) can be unlocked via an unspecified method.
The weakness was released 06/13/2023. It is possible to read the advisory at gov.il. This vulnerability is uniquely identified as CVE-2023-32219 since 05/04/2023. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 12/30/2025).
We expect the 0-day to have been worth approximately $25k-$100k.
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-2023-36477). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 6.5
CNA Vector (Israel National Cyber Directorate): 🔍
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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
05/04/2023 🔍06/13/2023 🔍
06/13/2023 🔍
12/30/2025 🔍
Sources
Advisory: gov.ilStatus: Not defined
CVE: CVE-2023-32219 (🔍)
GCVE (CVE): GCVE-0-2023-32219
GCVE (VulDB): GCVE-100-231291
EUVD: 🔍
Entry
Created: 06/13/2023 08:02Updated: 12/30/2025 08:58
Changes: 06/13/2023 08:02 (47), 01/06/2025 18:31 (36), 12/30/2025 08:58 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.