dbcve.org
Debian LinuxOperating system · Debian

CVE-2019-14562

MEDIUM · 5.5 CVSS v3.1 Published 2020-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Integer overflow in DxeImageVerificationHandler() EDK II may allow an authenticated user to potentially enable denial of service via local access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Integer overflow vulnerability in DxeImageVerificationHandler() function within EDK II (UEFI firmware development kit). The overflow occurs during image verification processing and can be triggered by an authenticated user with local access, leading to denial of service.

MitigationApply vendor-supplied firmware updates for affected systems using EDK II. Restrict physical and local access to systems to limit exposure to authenticated attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 9.0
Edk2Application
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm system uses UEFI firmware
    Check for /sys/firmware/efi directory or run 'ls /sys/firmware/efi'
    Affected if Directory exists, indicating the system uses UEFI firmware and may contain the vulnerable EDK II component
  2. Check UEFI firmware version
    Run 'sudo dmidecode -s bios-version' or 'sudo dmidecode -t bios' to retrieve the installed firmware version
    Affected if The reported firmware version falls within the affected range or is an unpatched EDK II-based firmware (all versions of Tianocore Edk2 are affected)
  3. Check for EDK II package on Debian
    Run 'dpkg -l | grep -i edk2' or 'dpkg -l | grep -i uefi' on Debian 9.0 systems
    Affected if The edk2 package is installed, indicating the vulnerable code is present in the firmware
  4. Check UEFI vendor information
    Run 'sudo dmidecode -s bios-vendor' to identify the firmware vendor and 'sudo dmidecode -s system-manufacturer' for system manufacturer
    Affected if Vendor uses EDK II as their firmware base and has not released patches for CVE-2019-14562
  5. Verify secure boot configuration
    Check /sys/firmware/efi/efivars/SecureBoot-* or run 'mokutil --sb-state' to see if secure boot is enabled
    Affected if Secure boot is disabled, as the vulnerability affects image verification processing in DxeImageVerificationHandler()

A system is affected if it runs UEFI firmware built with EDK II (Tianocore) and the firmware has not been patched, especially on Debian 9.0 systems or any EDK II-based firmware where secure boot is disabled and the attacker has local authenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates for affected systems using EDK II. Restrict physical and local access to systems to limit exposure to authenticated attackers.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14562 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data