# CVE-2018-14643: smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature

> Attackers can bypass authentication in Foreman's smart_proxy_dynflow to execute arbitrary commands with high privileges on managed machines.

- **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:** Yes
- **Published:** 21 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gx5g-xcxj-cx2w, RHSA-2018:2733

## What is CVE-2018-14643?

CVE-2018-14643 is a critical authentication bypass vulnerability in Theforeman Foreman, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman. A malicious attacker can use this flaw to remotely execute arbitrary commands on machines managed by vulnerable Foreman instances, in a highly privileged context.

Weakness: CWE-287 (Improper Authentication), CWE-592 (DEPRECATED: Authentication Bypass Issues)

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

4 open source packages ship an affected version, including smart_proxy_dynflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `smart_proxy_dynflow` | RubyGems | All versions | 0.1.11 |
| `smart_proxy_dynflow` | RubyGems | All versions | 0.1.11 |
| `smart_proxy_dynflow` | RubyGems | From 0.2.0 | 0.2.1 |
| `smart_proxy_dynflow` | RubyGems | From 0.2.0 | 0.2.1 |
| `rubygem-smart_proxy_dynflow` | Red Hat:satellite:6.3::el7 | All versions | 0:0.1.10.2-1.el7sat |
| `rubygem-smart_proxy_dynflow` | Red Hat:satellite_capsule:6.3::el7 | All versions | 0:0.1.10.2-1.el7sat |

Products: Theforeman Foreman.

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

Upgrade smart_proxy_dynflow to a fixed version for your release line: 0.1.11 or 0.2.1.

## Is CVE-2018-14643 being exploited?

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

## Other vulnerabilities in Theforeman Foreman

- [CVE-2017-7505](https://insights.sbomify.com/CVE-2017-7505/): Missing authorization in foreman (high 8.8)
- [CVE-2016-4475](https://insights.sbomify.com/CVE-2016-4475/): Missing authorization in n/a (high 8.8)
- [CVE-2016-3728](https://insights.sbomify.com/CVE-2016-3728/): Code injection in n/a (high 8.8)
- [CVE-2015-5246](https://insights.sbomify.com/CVE-2015-5246/): Auth bypass in n/a (high 8.1)
- [CVE-2015-5152](https://insights.sbomify.com/CVE-2015-5152/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14643 is a critical authentication bypass vulnerability in Theforeman Foreman, published on 21 Sep 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-14643 in the wild and no public exploit code.

Affected packages and fixed versions:
- smart_proxy_dynflow (RubyGems): affected all versions; fixed in 0.1.11
- smart_proxy_dynflow (RubyGems): affected all versions; fixed in 0.1.11
- smart_proxy_dynflow (RubyGems): affected from 0.2.0; fixed in 0.2.1
- smart_proxy_dynflow (RubyGems): affected from 0.2.0; fixed in 0.2.1

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

## Sources

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

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