CVE-2023-20814 json
In wlan service, there is a possible out of bounds write due to improper input validation.
published 2023-08-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-24993
- cvss
- 6.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
In wlan service, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07453560; Issue ID: ALPS07453560.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- MediaTek, Inc. MT6580, MT6739, MT6761, MT6765, MT6768, MT6779, MT6781, MT6833, MT6853, MT6853T, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6886, MT6889, MT6891, MT6893, MT6895, MT6983, MT6985
- mediatek mt6580
- mediatek mt6739
- mediatek mt6761
- mediatek mt6765
- mediatek mt6768
- mediatek mt6779
- mediatek mt6781
- mediatek mt6833
- mediatek mt6853
- mediatek mt6853t
- mediatek mt6855
- mediatek mt6873
- mediatek mt6875
- mediatek mt6877
- mediatek mt6879
- mediatek mt6883
- mediatek mt6885
- mediatek mt6886
- mediatek mt6889
- mediatek mt6891
- mediatek mt6893
- mediatek mt6895
- mediatek mt6983
- mediatek mt6985
- google android
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
corp.mediatek.com
/product-security-bulletin/August-2023
vendor-advisory
Sources
- CVE List CVE-2023-20814
- NVD CVE-2023-20814
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.