FedoraOperating system · Fedoraproject
CVE-2015-0278
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 · uneditedlibuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain privileges via unspecified vectors.
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 confidencelibuv before version 0.10.34 contains a privilege escalation vulnerability where group privileges are not properly dropped, potentially allowing context-dependent attackers to gain elevated group privileges.
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
= 21
Node.jsApplication
< 0.10.37<= 0.10.33CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed libuv versionRun `uv_version()` in code, or check the library file version with `ldd --version` or inspect the installed package: `rpm -q libuv` on Fedora or check node module dependenciesAffected if The version is 0.10.33 or earlier, or the version cannot be determined (assume vulnerable)
-
Identify the Node.js version if applicableRun `node --version` to check the Node.js interpreter versionAffected if Node.js version is earlier than 0.10.37 and it links to a vulnerable libuv version
-
Confirm the operating system is Fedora 21Run `cat /etc/fedora-release` or `cat /etc/redhat-release`Affected if Running Fedora 21 and the bundled libuv is version 0.10.33 or earlier
-
Determine if the application uses libuv privilege operationsAudit the application code to determine if it invokes libuv functions that handle group privileges (such as setuid, setgid, or group membership operations)Affected if The application uses libuv's group privilege handling functions while running with elevated group permissions on a vulnerable version
You are affected if you are running libuv version 0.10.33 or earlier (or Node.js < 0.10.37 on Fedora 21) AND your application uses libuv functionality that handles group privilege transitions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.10.37
Upgrade libuv to version 0.10.34 or later. Audit code paths that invoke libuv functionality to verify no custom privilege handling is in place that could bypass the fix.
libuv >= 0.10.34 OR Node.js >= 0.10.37
- Identify the current libuv version installed (e.g., run `uv --version` or check package manager)
- Upgrade libuv to version 0.10.34 or later via package manager or source compilation
- Alternatively, upgrade Node.js to version 0.10.37 or later, which bundles the fixed libuv version
- Restart any services or applications using libuv/Node.js to ensure the new version is loaded
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0278 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-0278 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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