CVE-2022-36439
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAsusSoftwareManager.exe in ASUS System Control Interface on ASUS personal computers (running Windows) allows a local user to write into the Temp directory and delete another more privileged file via SYSTEM privileges. This affects ASUS System Control Interface 3 before 3.1.5.0, AsusSoftwareManger.exe before 1.0.53.0, and AsusLiveUpdate.dll before 1.0.45.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAsusSoftwareManager.exe in ASUS System Control Interface contains a local privilege escalation vulnerability where an unprivileged local user can write files to the Temp directory that are then processed by a SYSTEM-privileged process, allowing deletion of arbitrary privileged files. This is a time-of-check-time-of-use (TOCTOU) or insecure temporary file handling issue.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.0.45.0< 1.0.53.0>= 3.0.0.0, < 3.1.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if ASUS System Control Interface is installedOpen Programs and Features (appwiz.cpl) or check C:\Program Files\ASUS\ for folders named 'System Control Interface' or similar ASUS software directories. Look for AsusSoftwareManager.exe or ASUS-related executables.Affected if ASUS System Control Interface version is >= 3.0.0.0 and < 3.1.5.0, or AsusSoftwareManager.exe version is < 1.0.53.0, or AsusLiveUpdate version is < 1.0.45.0
-
Locate AsusSoftwareManager.exe versionNavigate to the installation directory (commonly C:\Program Files\ASUS\ASUSSystemControlInterface or C:\Program Files (x86)\ASUS\), right-click AsusSoftwareManager.exe, select Properties, and view the File Version or Product Version in the Details tab.Affected if The Product Version shown is less than 1.0.53.0
-
Locate AsusLiveUpdate component versionLook for AsusLiveUpdate.dll or Asusliveupdate.exe in the ASUS installation directories. Right-click the file, select Properties, and check the File Version in the Details tab.Affected if The File Version is less than 1.0.45.0
-
Confirm ASUS System Control Interface versionIn Programs and Features, locate 'ASUS System Control Interface' or similar ASUS utility entries, note the version column, or check the version of the main executable in the installation folder.Affected if The installed version is 3.0.0.0 or higher but lower than 3.1.5.0
If any ASUS System Control Interface, AsusSoftwareManager, or AsusLiveUpdate component is present with a version falling within the affected ranges, the system is vulnerable to this privilege escalation flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.0.45.01.0.53.03.1.5.0
Update ASUS System Control Interface to version 3.1.5.0 or later, AsusSoftwareManager.exe to 1.0.53.0 or later, and AsusLiveUpdate.dll to 1.0.45.0 or later to remediate this vulnerability.
ASUS System Control Interface >= 3.1.5.0 | AsusSoftwareManager >= 1.0.53.0 | AsusLiveUpdate >= 1.0.45.0
- Identify which ASUS software is installed on the system (ASUS System Control Interface, AsusSoftwareManager, or AsusLiveUpdate)
- Check the current version of each installed component in Windows Settings > Apps & Features or via the application's Properties
- Download the fixed version from the official ASUS support website (asus.com) or through the ASUS live update utility
- Uninstall the current version of the affected software if the installer does not offer an in-place upgrade
- Install the updated version: ASUS System Control Interface 3.1.5.0 or later, AsusSoftwareManager 1.0.53.0 or later, or AsusLiveUpdate 1.0.45.0 or later
- Restart the system if prompted and verify the updated version is installed correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36439 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36439 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data