# CVE-2024-1695: Privilege escalation in HP Application Enabling Software Driver

> A vulnerability in the HP Application Enabling Software Driver allows attackers to escalate privileges on affected HP PC products.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-hmw2-fx34-2q97

## What is CVE-2024-1695?

CVE-2024-1695 is a medium-severity vulnerability in HP Application Enabling Software Driver, published on 6 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential security vulnerability has been identified in the HP Application Enabling Software Driver for certain HP PC products, which might allow escalation of privilege. HP is releasing software updates to mitigate this potential vulnerability.

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


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

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

## Is CVE-2024-1695 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1695 is a medium-severity vulnerability in HP Application Enabling Software Driver, published on 6 May 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-1695 in the wild and no public exploit code.

Affected product: HP Application Enabling Software Driver. 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-1695/ (Markdown: https://insights.sbomify.com/CVE-2024-1695/index.md)
```

## Sources

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

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