nday
CVE-2022-38699

ASUS Armoury Crate Service - Arbitrary File Creation via Elevation of Privilege Flaw

ASUS / Armoury Crate Service

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

link following
CWE-59, stated by the CNA twcert, NVD's analysts, and NVD, republishing [email protected]
physical
AV:P in CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (CVSS 3.1) from the CNA twcert
no user interaction
UI:N in CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (CVSS 3.1) from the CNA twcert
stage
DIS
disclosed
cvss
5.9 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2022-09-28T03:25Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:P
Physical: needs physical access to the device
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA twcert.

Event log

+DISdisclosed

CVE record published by twcert. CVSS 5.9, medium.

src cvelist · nday , bulk import · raw
{
  "id": 271937,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2022-38699",
  "occurred_at": "2022-09-28T03:25:34.591Z",
  "observed_at": "2026-11-13T05:37:45.178256Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
      "version": "3.1",
      "base_score": 5.9,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2025-05-21T14:54:09.894843Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2022-09-28T03:25:34.591Z",
    "assigner_short_name": "twcert"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.