dbcve.org
FedoraOperating system · Fedoraproject

CVE-2014-8119

HIGH · 7.5 CVSS v3.0 Published 2017-12-29
Fix available
A fix is available. Upgrade to after 0.2.6 or later.
See remediation →
84/100
Remediation priority · High
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
The find_ifcfg_path function in netcf before 0.2.7 might allow attackers to cause a denial of service (application crash) via vectors involving augeas path expressions.

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

The find_ifcfg_path function in netcf before version 0.2.7 processes augeas path expressions unsafely, allowing malicious or crafted path expressions to trigger an application crash resulting in denial of service.

MitigationUpgrade netcf to version 0.2.7 or later to patch the vulnerability. If immediate upgrade is not possible, restrict access to the netcf API and validate any user-controlled path expressions.

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
FedoraOperating system
Affected:= 20= 21= 22
Enterprise LinuxOperating system
Affected:= 6.0= 7.0
NetcfApplication
Affected:<= 0.2.6

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Check if netcf is installed
    Run 'rpm -q netcf' on RHEL/Fedora systems, or 'dpkg -l netcf' on Debian-based systems. On other systems, check for the netcf binary: 'which netcf' or 'ls -l /usr/sbin/netcf'
    Affected if netcf is not installed - not vulnerable. If installed, continue to version check.
  2. Determine installed netcf version
    Run 'rpm -q --qf "%{VERSION}-%{RELEASE}" netcf' on RPM-based systems, or 'dpkg -s netcf | grep Version' on Debian-based systems. Compare the version number to 0.2.6
    Affected if Version is 0.2.6 or earlier - the system is affected by this vulnerability. Version 0.2.7 and later are not affected.
  3. Verify augeas is in use
    Check if the netcf library is linked with augeas: 'ldd /usr/sbin/netcf 2>/dev/null | grep augeas' or 'rpm -q --requires netcf | grep augeas'
    Affected if augeas is not present - the specific exploitation vector may not apply, but the code vulnerability still exists in unpatched versions.
  4. Check for network configuration usage
    Review if netcf is being used to manage network interfaces. Check for configuration files in /etc/sysconfig/network-scripts/ (RHEL) or /etc/network/ (Debian) that may be processed by netcf, or look for netcf activity in logs
    Affected if netcf is actively used to manage network configuration - the vulnerable find_ifcfg_path function could be triggered during normal operation.
  5. Check for custom augeas lens paths
    Examine any custom configuration or scripts that invoke netcf with user-controlled path expressions. Search for files containing 'augeas' and 'path' patterns, or review netcf usage in any automation scripts
    Affected if Custom or user-supplied path expressions are passed to netcf - these could trigger the unsafe path expression processing.

The system is affected if netcf version 0.2.6 or earlier is installed AND the software is in use, regardless of whether specific exploitation conditions are currently present.

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
Upgrade available Upgrade to a release after 0.2.6
Interim mitigation

Upgrade netcf to version 0.2.7 or later to patch the vulnerability. If immediate upgrade is not possible, restrict access to the netcf API and validate any user-controlled path expressions.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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