An authentication bypass flaw was found in the smart_proxy_dynflow component used by Foreman.
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.
- Published
- Sep 21, 2018
- Updated
- Jun 16, 2026
- EPSS
- 6.1% · 93th percentile
- CWE
- CWE-592
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.1%
CNA vs NVD score
- NVD
- 9.8
- CNA · redhat
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| theforeman | foreman | cpe:2.3:a:theforeman:foreman |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- theforeman foremanall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
[UNKNOWN] smart_proxy_dynflow
- n/aaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:satellite_capsule:6.3::el7 | rubygem-smart_proxy_dynflow | before 0:0.1.10.2-1.el7sat | 0:0.1.10.2-1.el7sat |
| RubyGems | smart_proxy_dynflow | from 0.2.0 · before 0.2.1 | 0.2.1 |
| RubyGems | smart_proxy_dynflow | before 0.1.11 | 0.1.11 |
Same product
theforeman: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-0462Arbitrary code execution through yaml global parameters36Monitor
- CVE-2023-0118Foreman: arbitrary code execution through templates36Monitor
- CVE-2018-1097A flaw was found in foreman before 1.16.1.36Monitor
- CVE-2016-4475The (1) Organization and (2) Locations APIs and UIs in Foreman before 1.11.4 and 1.12.x before 1.12.0-RC3 allow remote authenticated users t36Monitor
- CVE-2016-3728Eval injection vulnerability in tftp_api.rb in the TFTP module in the Smart-Proxy in Foreman before 1.10.4 and 1.11.x before 1.11.2 allows r36Monitor
- CVE-2021-3590A flaw was found in Foreman project.35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:rubygem-smart_proxy_dynflow | 0:0.1.10.2-1.el7sat · Red Hat:satellite_capsule:6.3::el7 | Package registry (OSV) |
| RubyGems:smart_proxy_dynflow | 0.1.11 | Package registry (OSV) |
| RubyGems:smart_proxy_dynflow | 0.2.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-592 · DEPRECATED: Authentication Bypass IssuesCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.securityfocus.com/bid/105375
- access.redhat.com/errata/RHSA-2018:2733
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14643
- github.com/theforeman/smart_proxy_dynflow/pull/54
Vendor advisories and official records. Exploit/PoC links are deliberately left out.