dbcve.org
Agent Package AvailabilityApplication · Atera

CVE-2023-37243

HIGH · 7.8 CVSS v3.1 Published 2023-10-31
Fix available
A fix is available. Upgrade to 0.15.0.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
The C:\Windows\Temp\Agent.Package.Availability\Agent.Package.Availability.exe file is automatically launched as SYSTEM when the system reboots. Since the C:\Windows\Temp\Agent.Package.Availability folder inherits permissions from C:\Windows\Temp and Agent.Package.Availability.exe is susceptible to DLL hijacking, standard users can write a malicious DLL to it and elevate their privileges.

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 confidence

A DLL hijacking vulnerability exists where the Agent.Package.Availability.exe executable automatically runs as SYSTEM on system reboot from the C:\Windows\Temp\Agent.Package.Availability\ directory. Since this folder inherits the typically permissive C:\Windows\Temp permissions, standard users can place a malicious DLL in this location, causing it to be loaded by the elevated executable and achieving local privilege escalation to SYSTEM.

MitigationRestrict write permissions on the C:\Windows\Temp\Agent.Package.Availability\ folder to prevent standard users from writing files, and/or relocate the executable to a secure directory with controlled permissions, ensuring the application uses safe DLL search mode or explicit DLL paths.

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
Agent Package AvailabilityApplication
Affected:< 0.15.0.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if the vulnerable directory exists
    Inspect the directory C:\Windows\Temp\Agent.Package.Availability\ for existence and contents using File Explorer or command prompt (dir C:\Windows\Temp\Agent.Package.Availability\)
    Affected if The directory exists and contains Agent.Package.Availability.exe
  2. Verify executable version
    Right-click on Agent.Package.Availability.exe in C:\Windows\Temp\Agent.Package.Availability\, select Properties, and check the File version on the Details tab
    Affected if The executable version is lower than 0.15.0.0 or cannot be determined (indicating an unpatched version)
  3. Check directory permissions for standard users
    Right-click the C:\Windows\Temp\Agent.Package.Availability\ folder, go to Properties > Security, and examine what permissions Users or Standard users have
    Affected if Standard users have Write or Modify permissions to this folder, allowing them to place files
  4. Identify if the executable runs on reboot
    Check Task Scheduler (taskschd.msc) for a task named 'Agent.Package.Availability' or review registry Run keys for automatic startup entries related to this executable
    Affected if A scheduled task or startup entry runs Agent.Package.Availability.exe from the Temp directory on system boot

A system is affected if the C:\Windows\Temp\Agent.Package.Availability\ directory exists with the executable present, the version is below 0.15.0.0, and standard users have write access to that directory enabling DLL hijacking.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.15.0.0 or later
Fixed in 0.15.0.0
Interim mitigation

Restrict write permissions on the C:\Windows\Temp\Agent.Package.Availability\ folder to prevent standard users from writing files, and/or relocate the executable to a secure directory with controlled permissions, ensuring the application uses safe DLL search mode or explicit DLL paths.

Recommended fix Moderate confidence

Upgrade to Agent Package Availability version 0.15.0.0 or later

  1. Identify the current version of Agent Package Availability installed on the system
  2. Obtain the fixed version (0.15.0.0 or later) from the vendor's official GitHub repository or distribution channel
  3. Stop the Agent Package Availability service if it is currently running
  4. Upgrade the installation to version 0.15.0.0 or later following vendor documentation
  5. Restart the system or service to ensure the patched executable is loaded
  6. Verify that the C:\Windows\Temp\Agent.Package.Availability folder permissions are properly restricted and no longer allow standard users to write malicious DLLs

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agent Package Availability Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37243 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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