Skip to content
vulneraibility.com
Screener

CVE-2019-14287

In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, and can cause incorrect logging, by invoking sudo with a crafted user ID. For example, this allows bypass of !root configuration, and USER= logging, for a "sudo -u \#$((0xffffffff))" command.

CVSS
8.8High
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
63.8%chance of exploitation in the next 30 daystop 0.8% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
17 Oct 2019analysed here 12 Nov 2026

Summary

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • sudo_project:sudo
  • fedoraproject:fedora
  • debian:debian_linux
  • opensuse:leap
  • canonical:ubuntu_linux
  • netapp:element_software_management_node
  • redhat:openshift_container_platform
  • redhat:virtualization
  • redhat:enterprise_linux
  • redhat:enterprise_linux_desktop
  • redhat:enterprise_linux_eus
  • redhat:enterprise_linux_server
  • redhat:enterprise_linux_server_aus
  • redhat:enterprise_linux_server_tus
  • redhat:enterprise_linux_workstation

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 on Exploit-DB · 27 GitHub proofs of concept

Exploit-DB

GitHub proofs of concept

and 23 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 15 Oct 2019First public exploit or proof of concept
  2. 17 Oct 2019Published3 days later
  3. 5 Aug 2024CVE record last updated1,753 days (about 5 years) later
  4. 12 Nov 2026Analysed by vulneraibility.com830 days (about 2 years) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2019-14287 being exploited?

Not confirmed. CVE-2019-14287 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 64% probability of exploitation in the next 30 days.

How severe is CVE-2019-14287?

CVE-2019-14287 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-14287?

Yes. A fix has been recorded for CVE-2019-14287. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-14287 affect?

CVE-2019-14287 affects sudo_project:sudo, fedoraproject:fedora, debian:debian_linux, opensuse:leap, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

37 references in the CVE record, grouped by the tags the record gives them.

Advisories (23)

Show 17 more

Other links (14)

Show 8 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com