# CVE-2024-39755: Privilege escalation in Anka Build

> An attacker can execute privileged operations via a crafted PKG file in Veertu Anka Build, leading to privilege escalation.

- **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 Oct 2024
- **Updated:** 18 Dec 2024
- **Also known as:** GHSA-2jm4-m62p-325r

## What is CVE-2024-39755?

CVE-2024-39755 is a high-severity vulnerability in Veertu Anka Build, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability exists in the node update functionality of Veertu Anka Build 1.42.0. A specially crafted PKG file can lead to execute priviledged operation. An attacker can make an unauthenticated HTTP request to trigger this vulnerability.

Weakness: CWE-282 (Improper Ownership Management)

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

It affects 1 product.


Products: Veertu Anka Build Cloud.

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

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

## Is CVE-2024-39755 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39755 exists.

## Other vulnerabilities in Veertu Anka Build

- [CVE-2024-41163](https://insights.sbomify.com/CVE-2024-41163/): Path traversal in Anka Build (high 7.5)
- [CVE-2024-41922](https://insights.sbomify.com/CVE-2024-41922/): Path traversal in Anka Build (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39755 is a high-severity vulnerability in Veertu Anka Build, published on 3 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39755 exists.

Affected product: Veertu Anka Build. 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-39755/ (Markdown: https://insights.sbomify.com/CVE-2024-39755/index.md)
```

## Sources

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

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