# CVE-2024-6364: Server Identity Validation Bypass in Absolute Persistence®

> An attacker with physical access and network control can bypass server identity validation to execute OS commands on devices with inactive Absolute Persistence.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:P/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA: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:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-rmx6-3w23-whmj

## What is CVE-2024-6364?

CVE-2024-6364 is a medium-severity vulnerability in Absolute Persistence, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Absolute Persistence® versions before 2.8 exists when it is not activated. This may allow a skilled attacker with both physical access to the device, and full hostile network control, to initiate OS commands on the device.  To remediate this vulnerability, update the device firmware to the latest available version. Please contact the device manufacturer for upgrade instructions or contact Absolute Security, see reference below.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Absolute Persistence.

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

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

## Is CVE-2024-6364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6364 is a medium-severity vulnerability in Absolute Persistence, published on 13 May 2025. 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-6364 in the wild and no public exploit code.

Affected product: Absolute Persistence. 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-6364/ (Markdown: https://insights.sbomify.com/CVE-2024-6364/index.md)
```

## Sources

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

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