NVD / CVE Program· CNA redhat

CVE-2020-10759: A PGP signature bypass flaw was found in fwupd (all versions), which could lead to the installation of unsigned firmware.

Noroxi assessment

Priority: Monitor (action score 24/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.49% (FIRST EPSS).
Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: appstream-data (AlmaLinux:8) 8-20200724.el8; libxmlb (AlmaLinux:8) 0.1.15-1.el8; fwupd (Debian:12) 1.3.10-1.

Low priority for now. Upgrade to appstream-data (AlmaLinux:8) 8-20200724.el8; libxmlb (AlmaLinux:8) 0.1.15-1.el8; fwupd (Debian:12) 1.3.10-1 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

A PGP signature bypass flaw was found in fwupd (all versions), which could lead to the installation of unsigned firmware. As per upstream, a signature bypass is theoretically possible, but not practical because the Linux Vendor Firmware Service (LVFS) is either not implemented or enabled in versions of fwupd shipped with Red Hat Enterprise Linux 7 and 8. The highest threat from this vulnerability is to confidentiality and integrity.

MediumCVSS 6.0 · v3.1—Proof of concept Fix available

Weak crypto

Published: Sep 15, 2020
Updated: Jun 16, 2026
EPSS: 0.4% · 42th percentile
CWE: CWE-347

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 24 / 40 · 6.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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	enterprise linux	cpe:2.3:o:redhat:enterprise_linux

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
redhat enterprise linux8.0

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.

n/a fwupd
- all verions of fwupdaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	appstream-data	before 8-20200724.el8	8-20200724.el8
AlmaLinux:8	libxmlb	before 0.1.15-1.el8	0.1.15-1.el8
Debian:12	fwupd	before 1.3.10-1	1.3.10-1
Debian:12	libjcat	before 0.1.3-1	0.1.3-1
Debian:9	fwupd	before 0.7.4-2+deb9u1	0.7.4-2+deb9u1
openSUSE:Leap 15.1	fwupd	before 1.0.9-lp151.2.3.1	1.0.9-lp151.2.3.1
openSUSE:Leap 15.2	fwupd	before 1.2.14-lp152.3.9.1	1.2.14-lp152.3.9.1
openSUSE:Tumbleweed	fwupd	before 1.5.8-1.5	1.5.8-1.5
Red Hat:enterprise_linux:8::appstream	appstream-data	before 0:8-20200724.el8	0:8-20200724.el8
Red Hat:enterprise_linux:8::appstream	gnome-software	before 0:3.36.1-4.el8	0:3.36.1-4.el8
Red Hat:enterprise_linux:8::appstream	gnome-software-debuginfo	before 0:3.36.1-4.el8	0:3.36.1-4.el8
Red Hat:enterprise_linux:8::appstream	gnome-software-debugsource	before 0:3.36.1-4.el8	0:3.36.1-4.el8
Red Hat:enterprise_linux:8::baseos	fwupd	before 0:1.4.2-4.el8	0:1.4.2-4.el8
Red Hat:enterprise_linux:8::baseos	fwupd-debuginfo	before 0:1.4.2-4.el8	0:1.4.2-4.el8
Red Hat:enterprise_linux:8::baseos	fwupd-debugsource	before 0:1.4.2-4.el8	0:1.4.2-4.el8
Red Hat:enterprise_linux:8::baseos	libxmlb	before 0:0.1.15-1.el8	0:0.1.15-1.el8
Red Hat:enterprise_linux:8::baseos	libxmlb-debuginfo	before 0:0.1.15-1.el8	0:0.1.15-1.el8
Red Hat:enterprise_linux:8::baseos	libxmlb-debugsource	before 0:0.1.15-1.el8	0:0.1.15-1.el8
Red Hat:enterprise_linux:8::baseos	libxmlb-tests-debuginfo	before 0:0.1.15-1.el8	0:0.1.15-1.el8
Rocky Linux:8	appstream-data	before 0:8-20200724.el8	0:8-20200724.el8
Rocky Linux:8	libxmlb	before 0:0.1.15-1.el8	0:0.1.15-1.el8
SUSE:Linux Enterprise Module for Desktop Applications 15 SP1	fwupd	before 1.0.9-6.3.1	1.0.9-6.3.1
SUSE:Linux Enterprise Module for Desktop Applications 15 SP2	fwupd	before 1.2.14-5.8.2	1.2.14-5.8.2

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2015-3246libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, directly modifies /etc/passwd, wKEV
62This week
CVE-2023-50387Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of ser
60This week
CVE-2017-5456A mechanism to bypass file system access protections in the sandbox using the file system request constructor through an IPC message.
40Plan

Published before and after this one in the same product

← EarlierCVE-2020-2732Apr 8, 2020 · A flaw was discovered in the way that the KVM hypervisor handled instruction emulation for an L2 guest when nested virtualisation is enabled
27Monitor
← EarlierCVE-2020-10769Jun 26, 2020 · A buffer over-read flaw was found in RH kernel versions before 5.0 in crypto_authenc_extractkeys in crypto/authenc.c in the IPsec Cryptograp
22Monitor
Later →CVE-2020-25661Nov 5, 2020 · A Red Hat only CVE-2020-12351 regression issue was found in the way the Linux kernel's Bluetooth implementation handled L2CAP packets with A
36Monitor

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
almalinux:appstream-data	8-20200724.el8 · AlmaLinux:8	Package registry (OSV)
almalinux:libxmlb	0.1.15-1.el8 · AlmaLinux:8	Package registry (OSV)
debian:fwupd	1.3.10-1 · Debian:12	Package registry (OSV)
debian:libjcat	0.1.3-1 · Debian:12	Package registry (OSV)
opensuse:fwupd	1.0.9-lp151.2.3.1 · openSUSE:Leap 15.1	Package registry (OSV)
red hat:appstream-data	0:8-20200724.el8 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:fwupd	0:1.4.2-4.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:fwupd-debuginfo	0:1.4.2-4.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:fwupd-debugsource	0:1.4.2-4.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:gnome-software	0:3.36.1-4.el8 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:gnome-software-debuginfo	0:3.36.1-4.el8 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:gnome-software-debugsource	0:3.36.1-4.el8 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:libxmlb	0:0.1.15-1.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:libxmlb-debuginfo	0:0.1.15-1.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:libxmlb-debugsource	0:0.1.15-1.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
red hat:libxmlb-tests-debuginfo	0:0.1.15-1.el8 · Red Hat:enterprise_linux:8::baseos	Package registry (OSV)
rocky linux:appstream-data	0:8-20200724.el8 · Rocky Linux:8	Package registry (OSV)
rocky linux:libxmlb	0:0.1.15-1.el8 · Rocky Linux:8	Package registry (OSV)
suse:fwupd	1.0.9-6.3.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP1	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2020-06-06

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.

First PoCJun 6, 2020-102 d
PublishedSep 15, 2020
TodayNov 9, 2026+2246 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, 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

Someone with local access to the system can trigger it.
Administrator privileges are 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: none

Attack vector: Local
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

nvd-primary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const claims = jwt.verify(token, publicKey);

Fixed

1const claims = jwt.verify(token, publicKey, {
2  algorithms: ["RS256"],
3  issuer: "https://id.example.com",
4  audience: "portal",
5});

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

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

bugzilla.redhat.com/show_bug.cgi?id=1844316

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records