dbcve.org
LeapOperating system · Opensuse

CVE-2019-18903

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A Use After Free vulnerability in wicked of SUSE Linux Enterprise Server 12, SUSE Linux Enterprise Server 15; openSUSE Leap 15.1, Factory allows remote attackers to cause DoS or potentially code execution. This issue affects: SUSE Linux Enterprise Server 12 wicked versions prior to 0.6.60-2.18.1. SUSE Linux Enterprise Server 15 wicked versions prior to 0.6.60-28.26.1. openSUSE Leap 15.1 wicked versions prior to 0.6.60-lp151.2.9.1. openSUSE Factory wicked versions prior to 0.6.62.

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 · high confidence

A Use After Free (UAF) vulnerability exists in the wicked network management daemon on SUSE Linux Enterprise Server and openSUSE systems. The vulnerability allows remote attackers to cause denial of service or potentially execute arbitrary code by exploiting improper memory management where memory is accessed after being freed.

MitigationApply the vendor-supplied patches for the specific wicked versions (0.6.60-2.18.1 for SLES 12, 0.6.60-28.26.1 for SLES 15, 0.6.60-lp151.2.9.1 for Leap 15.1, or 0.6.62 for Factory). If patching is not immediately possible, restrict network access to the wicked service via firewall rules.

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
LeapOperating system
Affected:= 15.1
Linux Enterprise ServerOperating system
Affected:= 12= 15

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify installed wicked version
    Run 'rpm -q wicked' or 'zypper info wicked' to retrieve the installed package version
    Affected if The version is 0.6.60-2.18.1 or earlier on SLES 12, 0.6.60-28.26.1 or earlier on SLES 15, or 0.6.60-lp151.2.9.1 or earlier on Leap 15.1
  2. Confirm wicked daemon is active
    Run 'systemctl is-active wickedd' or 'systemctl status wicked' to check if the service is running
    Affected if The service is active and the version from step 1 falls within the affected ranges
  3. Verify package source repository
    Run 'rpm -qa --queryformat "%{NAME} %{VERSION}-%{RELEASE} %{VENDOR}\n" | grep wicked' to see which repository the package originated from
    Affected if The package originates from a vendor repository but remains at an unpatched version within the affected ranges

You are affected if the wicked network management daemon is installed and running with a version at or below the threshold for your specific SUSE product (0.6.60-2.18.1 for SLES 12, 0.6.60-28.26.1 for SLES 15, or 0.6.60-lp151.2.9.1 for Leap 15.1).

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches for the specific wicked versions (0.6.60-2.18.1 for SLES 12, 0.6.60-28.26.1 for SLES 15, 0.6.60-lp151.2.9.1 for Leap 15.1, or 0.6.62 for Factory). If patching is not immediately possible, restrict network access to the wicked service via firewall rules.

Recommended fix High confidence

wicked 0.6.60-2.18.1 (SLE12), 0.6.60-28.26.1 (SLE15), 0.6.60-lp151.2.9.1 (Leap 15.1), or 0.6.62 (Factory)

  1. Identify the currently installed wicked version using: zypper info wicked or rpm -q wicked
  2. For SUSE Linux Enterprise Server 12: Run zypper update wicked to upgrade to version 0.6.60-2.18.1 or later
  3. For SUSE Linux Enterprise Server 15: Run zypper update wicked to upgrade to version 0.6.60-28.26.1 or later
  4. For openSUSE Leap 15.1: Run zypper update wicked to upgrade to version 0.6.60-lp151.2.9.1 or later
  5. For openSUSE Factory: Run zypper update wicked to upgrade to version 0.6.62 or later
  6. After upgrading, restart the wicked service using: systemctl restart wickedd or systemctl restart wicked
  7. Verify the installed version matches or exceeds the fixed version using: rpm -q wicked
Caveat Service restart required for wicked daemon; ensure network connectivity is stable before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Leap Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18903 — 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-18903 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