rpm-ostree-client: fails to check gpg package signatures when layering
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Project Atomic | rpm-ostree, | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux Atomic Host 7 | |||
| rpm-ostree-0:2017.1-5.atomic.el7 | cpe:/a:redhat:rhel_atomic:7 | RHSA-2017:0444 | 2017-03-02T00:00:00Z |
| rpm-ostree-client-0:2017.1-6.atomic.el7 | cpe:/a:redhat:rhel_atomic:7 | RHSA-2017:0444 | 2017-03-02T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-11784 | 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. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 1.0% (1.013% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.