# CVE-2024-28033: Command injection in WebProxy

> Remote unauthenticated attackers can execute arbitrary OS commands on WebProxy servers, requiring users to discontinue use due to lack of developer support.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x23x-5mrc-48fh

## What is CVE-2024-28033?

CVE-2024-28033 is a high-severity command injection vulnerability in LunarNight Laboratory WebProxy, published on 26 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS command injection vulnerability exists in WebProxy 1.7.8 and 1.7.9, which may allow a remote unauthenticated attacker to execute an arbitrary OS command with the privilege of the running web server. Note that the developer was unreachable, therefore, users should consider stop using WebProxy 1.7.8 and 1.7.9.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-28033 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28033 is a high-severity command injection vulnerability in LunarNight Laboratory WebProxy, published on 26 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-28033 in the wild and no public exploit code.

Affected product: LunarNight Laboratory WebProxy. 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-28033/ (Markdown: https://insights.sbomify.com/CVE-2024-28033/index.md)
```

## Sources

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

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