CVE-2022-38699 json
ASUS Armoury Crate Service - Arbitrary File Creation via Elevation of Privilege Flaw
published 4y ago modified 4mo ago also EUVD-2022-41268
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
Armoury Crate Service’s logging function has insufficient validation to check if the log file is a symbolic link. A physical attacker with general user privilege can modify the log file property to a symbolic link that points to arbitrary system file, causing the logging function to overwrite the system file and disrupt the system.
Patch / fix
- asus armoury_crate_service 5.2.10.0
Is CVE-2022-38699 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected products
- ASUS Armoury Crate Service
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
twcert.org.tw
/tw/cp-132-6522-4eacb-1.html
third-party-advisory
Sources
- CVE List CVE-2022-38699
- NVD CVE-2022-38699
Fencer Intel 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.