CVE-2017-2623: It was discovered that rpm-ostree and rpm-ostree-client before 2017.3 fail to properly check GPG signatures on packages when doing layering.
Noroxi assessment
Priority: Monitor (action score 21/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% (FIRST EPSS); higher than 63.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: rpm-ostree (Red Hat:rhel_atomic:7) 0:2017.1-5.atomic.el7; rpm-ostree-client (Red Hat:rhel_atomic:7) 0:2017.1-6.atomic.el7; rpm-ostree-client-debuginfo (Red Hat:rhel_atomic:7) 0:2017.1-6.atomic.el7.
Low priority for now. Upgrade to rpm-ostree (Red Hat:rhel_atomic:7) 0:2017.1-5.atomic.el7; rpm-ostree-client (Red Hat:rhel_atomic:7) 0:2017.1-6.atomic.el7; rpm-ostree-client-debuginfo (Red Hat:rhel_atomic:7) 0:2017.1-6.atomic.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
It was discovered that rpm-ostree and rpm-ostree-client before 2017.3 fail to properly check GPG signatures on packages when doing layering. Packages with unsigned or badly signed content could fail to be rejected as expected. This issue is partially mitigated on RHEL Atomic Host, where certificate pinning is used by default.
- Published
- Jul 27, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-295
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CNA vs NVD score
- NVD
- 5.3
- CNA · redhat
- 5.3
- agree
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.
Check your site's encryptionRun the SSL check
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 |
|---|---|---|
| rpm-ostree | rpm-ostree | cpe:2.3:a:rpm-ostree:rpm-ostree |
| rpm-ostree | rpm-ostree-client | cpe:2.3:a:rpm-ostree:rpm-ostree-client |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Project Atomic rpm-ostree,
- 2017.3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise linux7.0
- rpm-ostree rpm-ostreebefore 2017.3
- rpm-ostree rpm-ostree-clientbefore 2017.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:rhel_atomic:7 | rpm-ostree | before 0:2017.1-5.atomic.el7 | 0:2017.1-5.atomic.el7 |
| Red Hat:rhel_atomic:7 | rpm-ostree-client | before 0:2017.1-6.atomic.el7 | 0:2017.1-6.atomic.el7 |
| Red Hat:rhel_atomic:7 | rpm-ostree-client-debuginfo | before 0:2017.1-6.atomic.el7 | 0:2017.1-6.atomic.el7 |
| Red Hat:rhel_atomic:7 | rpm-ostree-debuginfo | before 0:2017.1-5.atomic.el7 | 0:2017.1-5.atomic.el7 |
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:rpm-ostree | 0:2017.1-5.atomic.el7 · Red Hat:rhel_atomic:7 | Package registry (OSV) |
| red hat:rpm-ostree-client | 0:2017.1-6.atomic.el7 · Red Hat:rhel_atomic:7 | Package registry (OSV) |
| red hat:rpm-ostree-client-debuginfo | 0:2017.1-6.atomic.el7 · Red Hat:rhel_atomic:7 | Package registry (OSV) |
| red hat:rpm-ostree-debuginfo | 0:2017.1-5.atomic.el7 · Red Hat:rhel_atomic:7 | 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.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()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)
ATT&CK techniques
—
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.