Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Project Atomic | rpm-ostree, | 2017.3 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Red Hat
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Red Hat Rhel Atomic 7 | rpm-ostree | 2017.1-5.atomic.el7 | RHSA-2017:0444 |
| Red Hat Rhel Atomic 7 | rpm-ostree-client | 2017.1-6.atomic.el7 | RHSA-2017:0444 |
Advisories 1
- RHSA-2017:0444 Red Hat Security Advisory: rpm-ostree and rpm-ostree-client security, bug fix, and enhancement update Red Hat Security Advisories (RHSA) · Jul 1, 2026
References
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2623
- RHSA-2017:0444 vendor-advisory
- 96558 vdb-entry