CVE-2014-4870
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/opt/vyatta/bin/sudo-users/vyatta-clear-dhcp-lease.pl on the Brocade Vyatta 5400 vRouter 6.4R(x), 6.6R(x), and 6.7R1 does not properly validate parameters, which allows local users to gain privileges by leveraging the sudo configuration.
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 confidenceA Perl script (vyatta-clear-dhcp-lease.pl) in Brocade Vyatta 5400 vRouter versions 6.4R(x), 6.6R(x), and 6.7R1 runs with sudo privileges but fails to properly validate input parameters, allowing local unprivileged users to inject commands and escalate to root 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= 6.4= 6.6= 6.7all versionsCVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Locate the vulnerable Perl scriptSearch for the file vyatta-clear-dhcp-lease.pl on the system using: find / -name 'vyatta-clear-dhcp-lease.pl' 2>/dev/nullAffected if The file exists on the system (found at typical path /opt/vyatta/sbin/vyatta-clear-dhcp-lease.pl)
-
Check sudo permissions on the scriptRun: sudo -l | grep vyatta-clear-dhcp-lease.pl or check /etc/sudoers for entries containing this scriptAffected if The script is listed in sudoers or sudo -l shows it as allowed for execution without password
-
Verify the installed Vyatta versionCheck the installed version by running: vyatta-show-version or cat /opt/vyatta/etc/versionAffected if The version matches 6.4, 6.6, or 6.7 (or any version if 'all versions' applies per the advisory)
-
Confirm unprivileged user accessAs a non-root user, verify ability to execute commands on the system and check if they belong to groups that can run the affected scriptAffected if A non-root user exists with access to run the script via sudo
A user is affected if the vyatta-clear-dhcp-lease.pl script exists, is accessible via sudo for unprivileged users, and the Vyatta vRouter version is 6.4, 6.6, 6.7, or falls within the 'all versions' scope.
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.
From vendor dataApply vendor patches for CVE-2014-4870; alternatively, restrict or remove sudo permissions for the affected script until a patch is available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4870 — 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-2014-4870 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