# CVE-2024-28519: Privilege escalation in n/a

> A kernel handle leak in eScan Antivirus allows low-privileged users to escalate privileges on the system.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 May 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-78m2-r6wc-m75w

## What is CVE-2024-28519?

CVE-2024-28519 is a high-severity vulnerability in n/a, published on 3 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A kernel handle leak issue in ProcObsrvesx.sys 4.0.0.49 in MicroWorld Technologies Inc eScan Antivirus could allow privilege escalation for low-privileged users.

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


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

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

## Is CVE-2024-28519 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28519 is a high-severity vulnerability in n/a, published on 3 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-28519 in the wild and no public exploit code.

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

## Sources

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

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