# CVE-2024-40872: Elevation of privilege in Absolute Secure Access clients and servers

> Local attackers with valid credentials can elevate privileges to system level by manipulating process tokens in Absolute Secure Access components.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3gx2-67xw-9fc9

## What is CVE-2024-40872?

CVE-2024-40872 is a high-severity vulnerability in Absolute Security Secure Access, published on 25 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an elevation of privilege vulnerability in server
and client components of Absolute Secure Access prior to version 13.07.
Attackers with local access and valid desktop user credentials can elevate
their privilege to system level by passing invalid address data to the vulnerable
component. This could be used to
manipulate process tokens to elevate the privilege of a normal process to
System. The scope is changed, the impact to system confidentiality and
integrity is high, the impact to the availability of the effected component is
none.

Weakness: CWE-822 (Untrusted Pointer Dereference)

## Which versions are affected by CVE-2024-40872?


## How do I fix CVE-2024-40872?

No fix has been published for CVE-2024-40872 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-40872 being exploited?

There is no known exploitation of CVE-2024-40872 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40872 and fix it if it is affected.

What it is: CVE-2024-40872 is a high-severity vulnerability in Absolute Security Secure Access, published on 25 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-40872 in the wild and no public exploit code.

Affected product: Absolute Security Secure Access. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-40872/ (Markdown: https://insights.sbomify.com/CVE-2024-40872/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-40872
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-40872
- OSV: https://osv.dev/vulnerability/CVE-2024-40872

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-40872/
Summaries are generated and may contain mistakes; the official description above is the record.