CVE-2019-3844

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), public exploit)
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.8Exploit: Exploit-DB (verified) · public exploitExposed services: Not assessed

A fix is available — apply it.

It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
61
EG Risk 61/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation65% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 26, 2019

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Sep 30, 2026
Patch available. Sources: redhat.
generic

Pony Mail

https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
redhatMentions a patch (unverified)

1684610 – (CVE-2019-3844) CVE-2019-3844 systemd: services with DynamicUser can get new privileges and create SGID binaries

Affected: Red Hat Enterprise Linux 7 as they did not include support for DynamicUser property.

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3844
generic

CVE-2019-3844 - PSIRT.COM

http://www.securityfocus.com/bid/108096
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20190619-0002/

Vendor Advisories for CVE-2019-3844(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuudev-udeb (229-4ubuntu21.27) @ xenial2026-05-27ubuntu
redhatsystemd-0:239-29.el82020-04-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
systemd—
  • every version up to 242-4: fixed in 242-4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
systemd—
  • every version up to 242-4: fixed in 242-4
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
systemd—
  • every version up to 242-4: fixed in 242-4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
systemd—
  • every version up to 242-4: fixed in 242-4
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 16:37 UTCEPSS rescore
  3. 2026-10-07 23:43 UTCEPSS rescore
  4. 2026-10-06 15:13 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-04 23:18 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 10:23 UTCEG score recompute
  10. 2026-09-28 13:46 UTCEPSS rescore
  11. 2026-09-28 07:32 UTCOSV refresh
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:54 UTCEPSS rescore
  14. 2026-09-26 00:20 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-22 14:43 UTCEPSS rescore
  17. 2026-09-21 20:28 UTCEPSS rescore
  18. 2026-09-20 20:11 UTCEPSS rescore
  19. 2026-09-19 15:37 UTCEPSS rescore
  20. 2026-09-18 19:23 UTCEPSS rescore
  21. 2026-09-17 19:22 UTCEPSS rescore
  22. 2026-09-16 14:04 UTCEPSS rescore
  23. 2026-09-15 03:06 UTCEPSS rescore
  24. 2026-09-13 16:42 UTCEPSS rescore
  25. 2026-09-12 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:48 UTCEPSS rescore
  2. 2026-09-11 09:32 UTCEPSS rescore
  3. 2026-09-08 21:55 UTCEPSS rescore
  4. 2026-09-08 11:58 UTCOSV refresh
  5. 2026-09-07 15:57 UTCEPSS rescore
  6. 2026-09-06 13:44 UTCEPSS rescore
  7. 2026-09-05 15:24 UTCEPSS rescore
  8. 2026-09-04 13:56 UTCEPSS rescore
  9. 2026-09-02 14:08 UTCEPSS rescore
  10. 2026-09-01 03:32 UTCEPSS rescore
  11. 2026-08-30 01:18 UTCEPSS rescore
  12. 2026-08-27 14:21 UTCEPSS rescore
  13. 2026-08-26 14:42 UTCEPSS rescore
  14. 2026-08-25 13:45 UTCEPSS rescore
  15. 2026-08-21 22:44 UTCOSV refresh
  16. 2026-08-19 17:00 UTCEPSS rescore
  17. 2026-08-18 13:44 UTCEPSS rescore
  18. 2026-08-17 13:43 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-13 21:57 UTCEPSS rescore
  21. 2026-08-12 13:47 UTCEPSS rescore
  22. 2026-08-09 13:43 UTCEPSS rescore
  23. 2026-08-08 16:33 UTCEPSS rescore
  24. 2026-08-07 16:23 UTCEPSS rescore
  25. 2026-08-06 04:51 UTCOSV refresh
  26. 2026-08-05 19:13 UTCEPSS rescore
  27. 2026-08-04 15:05 UTCEPSS rescore
  28. 2026-08-04 10:34 UTCEPSS rescore
  29. 2026-08-03 10:32 UTCEPSS rescore
  30. 2026-08-02 02:23 UTCEPSS rescore
  31. 2026-08-01 04:12 UTCEPSS rescore
  32. 2026-07-30 16:24 UTCEPSS rescore
  33. 2026-07-30 01:27 UTCEPSS rescore
  34. 2026-07-28 15:32 UTCEPSS rescore
  35. 2026-07-26 14:51 UTCEPSS rescore
  36. 2026-07-25 14:14 UTCEPSS rescore
  37. 2026-07-24 14:14 UTCEPSS rescore
  38. 2026-07-23 14:15 UTCEPSS rescore
  39. 2026-07-23 01:45 UTCEG score recompute
  40. 2026-07-22 22:26 UTCEG score recompute
  41. 2026-07-22 14:05 UTCEPSS rescore
  42. 2026-07-21 15:22 UTCEPSS rescore
  43. 2026-07-21 15:22 UTCEPSS rescore
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-20 17:02 UTCOSV refresh
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-19 02:26 UTCEPSS rescore
  50. 2026-07-18 10:02 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-16 16:59 UTCEPSS rescore
  53. 2026-07-15 16:55 UTCEPSS rescore
  54. 2026-07-15 01:57 UTCEPSS rescore
  55. 2026-07-13 22:27 UTCEPSS rescore
  56. 2026-07-13 22:27 UTCEPSS rescore
  57. 2026-07-13 06:10 UTCEPSS rescore
  58. 2026-07-13 06:10 UTCEPSS rescore
  59. 2026-07-12 05:44 UTCEPSS rescore
  60. 2026-07-12 05:43 UTCEPSS rescore
  61. 2026-07-11 08:24 UTCEPSS rescore
  62. 2026-07-11 08:24 UTCEPSS rescore
  63. 2026-07-09 19:06 UTCEPSS rescore
  64. 2026-07-08 15:11 UTCEPSS rescore
  65. 2026-07-07 13:43 UTCEPSS rescore
  66. 2026-07-06 16:25 UTCEPSS rescore
  67. 2026-07-06 16:25 UTCEPSS rescore
  68. 2026-07-06 02:20 UTCEPSS rescore
  69. 2026-07-06 02:20 UTCEPSS rescore
  70. 2026-07-05 02:27 UTCEPSS rescore
  71. 2026-07-04 06:28 UTCEPSS rescore
  72. 2026-07-03 12:26 UTCOSV refresh
  73. 2026-07-01 15:03 UTCEPSS rescore
  74. 2026-07-01 15:03 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46760✓ verified
    First seen Apr 26, 2019

    systemd - DynamicUser can Create setuid Binaries when Assisted by Another Process

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-3844?
CVE-2019-3844 is a high vulnerability published on April 26, 2019. It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will…
When was CVE-2019-3844 disclosed?
CVE-2019-3844 was first published on April 26, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-3844 actively exploited?
CVE-2019-3844 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-3844?
CVE-2019-3844 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2019-3844?
A fix for CVE-2019-3844 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-3844 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-3844

Explore →

Is Your Infrastructure Affected by CVE-2019-3844?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs