CVE-2016-8631: The OpenShift Enterprise 3 router does not properly sort routes when processing newly added routes.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: atomic-openshift (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7; atomic-openshift-clients (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7; atomic-openshift-clients-redistributable (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7.
Low priority for now. Upgrade to atomic-openshift (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7; atomic-openshift-clients (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7; atomic-openshift-clients-redistributable (Red Hat:openshift:3.3::el7) 0:3.3.1.4-1.git.0.7c8657c.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The OpenShift Enterprise 3 router does not properly sort routes when processing newly added routes. An attacker with access to create routes can potentially overwrite existing routes and redirect network traffic for other users to their own site.
- Published
- Jul 31, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-20
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CNA vs NVD score
- NVD
- 7.7
- CNA · redhat
- 6.3
- 1.4 point gap
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | openshift | cpe:2.3:a:redhat:openshift |
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.
Red Hat Openshift Enterprise
- 3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat openshift3.0
- redhat openshift3.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:openshift:3.3::el7 | atomic-openshift | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-clients | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-clients-redistributable | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-dockerregistry | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-master | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-node | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-pod | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-sdn-ovs | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | atomic-openshift-tests | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
| Red Hat:openshift:3.3::el7 | tuned-profiles-atomic-openshift-node | before 0:3.3.1.4-1.git.0.7c8657c.el7 | 0:3.3.1.4-1.git.0.7c8657c.el7 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-3496cartridge_repository.rb in OpenShift Origin and Enterprise 1.2.8 through 2.1.1 allows remote attackers to execute arbitrary commands via…42Plan
- CVE-2013-2060The download_from_url function in OpenShift Origin allows remote attackers to execute arbitrary commands via shell metacharacters in the…41Plan
- CVE-2014-0234The default configuration of broker.conf in Red Hat OpenShift Enterprise 2.x before 2.1 has a password of "mooo" for a Mongo account, which…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-10885Jul 5, 2018 · In atomic-openshift before version 3.10.9 a malicious network-policy configuration can cause Openshift Routing to crash when using…30Monitor
- ← EarlierCVE-2017-15137Jul 16, 2018 · The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example.21Monitor
- Later →CVE-2016-8651Aug 1, 2018 · An input validation flaw was found in the way OpenShift 3 handles requests for images.14Monitor
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:atomic-openshift | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-dockerregistry | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-master | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-node | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-pod | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-sdn-ovs | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:atomic-openshift-tests | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | Package registry (OSV) |
| red hat:tuned-profiles-atomic-openshift-node | 0:3.3.1.4-1.git.0.7c8657c.el7 · Red Hat:openshift:3.3::el7 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.