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

> Remote attackers can execute arbitrary code on Comodo UTM Firewall web consoles without authentication via crafted URLs.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 29 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7479-2r5v-v4vj

## What is CVE-2018-17431?

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

### Official description

Web Console in Comodo UTM Firewall before 2.7.0 allows remote attackers to execute arbitrary code without authentication via a crafted URL.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Comodo Unified Threat Management Firewall.

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

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

## Is CVE-2018-17431 being exploited?

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

Public exploit code:

- Proof of consept for CVE-2018-17431 (github_poc): https://github.com/Fadavvi/CVE-2018-17431-PoC
- Comodo Unified Threat Management Web Console 2.7.0 - Remote Code Execution (exploitdb)
- Comodo  (github_poc): https://github.com/sanan2004/CVE-2018-17431-Comodo
- Comodo Unified Threat Management Web Console - Remote Code Execution (nuclei): http/cves/2018/CVE-2018-17431.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17431 is a critical authentication bypass vulnerability in n/a, published on 29 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17431 exists.

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-17431/ (Markdown: https://insights.sbomify.com/CVE-2018-17431/index.md)
```

## Sources

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

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