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

> Local low-privileged attackers can execute arbitrary code and escalate privileges via insecure DLL loading in Axigen Mail Server for Windows.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/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:** 3 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6xj8-67w9-54rv

## What is CVE-2024-28589?

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

### Official description

An issue was discovered in Axigen Mail Server for Windows versions 10.5.18 and before, allows local low-privileged attackers to execute arbitrary code and escalate privileges via insecure DLL loading from a world-writable directory during service initialization.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2024-28589 being exploited?

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

Public exploit code:

- Local Privilege Escalation Vulnerability on Axigen for Windows (github_poc): https://github.com/Alaatk/CVE-2024-28589

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28589 is a medium-severity vulnerability in n/a, published on 3 Apr 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-28589 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-28589/ (Markdown: https://insights.sbomify.com/CVE-2024-28589/index.md)
```

## Sources

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

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