# CVE-2018-7739: Auth bypass in n/a

> Remote attackers can bypass authentication and gain root access via input validation flaws in the login process of Antsle Antman.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3g73-w5wg-gv2r

## What is CVE-2018-7739?

CVE-2018-7739 is a critical authentication bypass vulnerability in n/a, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

antsle antman before 0.9.1a allows remote attackers to bypass authentication via invalid characters in the username and password parameters, as demonstrated by a username=>&password=%0a string to the /login URI. This allows obtaining root permissions within the web management console, because the login process uses Java's ProcessBuilder class and a bash script called antsle-auth with insufficient input validation.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-7739?

It affects 1 product.


Products: Antsle Antman.

## How do I fix CVE-2018-7739?

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

## Is CVE-2018-7739 being exploited?

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

Public exploit code:

- antMan < 0.9.1a - Authentication Bypass (exploitdb)
- antMan 0.9.0c - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7739 and fix it if it is affected.

What it is: CVE-2018-7739 is a critical authentication bypass vulnerability in n/a, published on 6 Mar 2018. 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-2018-7739 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-2018-7739/ (Markdown: https://insights.sbomify.com/CVE-2018-7739/index.md)
```

## Sources

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

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