CVE-2014-3418
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 · uneditedconfig/userAdmin/login.tdf in Infoblox NetMRI before 6.8.5 allows remote attackers to execute arbitrary commands via shell metacharacters in the skipjackUsername parameter.
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 confidenceInfoblox NetMRI before version 6.8.5 contains a command injection vulnerability in the config/userAdmin/login.tdf authentication component. The skipjackUsername parameter accepts shell metacharacters without proper sanitization, allowing remote attackers to execute arbitrary OS commands on the NetMRI appliance.
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.8.4= 6.0.2.42= 6.1.2= 6.2.1= 6.2.1.48= 6.8.2.11CVSS 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 NetMRI installationLocate NetMRI installation directory or check system services for Infoblox NetMRI components. Common paths may include /opt/infoblox or check running processes for netmri-related services.Affected if NetMRI is not installed on the system
-
Determine installed NetMRI versionAccess the NetMRI admin interface or check version files within the installation directory. Look for a version file or access the /info endpoint if available.Affected if Installed version matches <= 6.8.4, 6.0.2.42, 6.1.2, 6.2.1, 6.2.1.48, or 6.8.2.11
-
Verify the login.tdf component existsCheck for the presence of the file config/userAdmin/login.tdf within the NetMRI web application directory.Affected if The login.tdf file exists and the version is in the affected range
-
Check if web interface is exposedDetermine if the NetMRI web interface is accessible from network locations. Review firewall rules and network ACLs allowing access to ports 80/443 or the configured NetMRI web port.Affected if Web interface is externally accessible and version is in the affected range
You are affected if Infoblox NetMRI is installed and the installed version matches 6.0.2.42, 6.1.2, 6.2.1, 6.2.1.48, 6.8.2.11, or any version <= 6.8.4 with the login.tdf component accessible.
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 · scopedUpgrade to NetMRI version 6.8.5 or later which contains the patch for this vulnerability. If immediate upgrade is not possible, implement web application firewall rules to block shell metacharacters in authentication parameters as a temporary compensating control.
Infoblox NetMRI 6.8.5 or later
- Upgrade Infoblox NetMRI to version 6.8.5 or later to resolve the OS command injection vulnerability in config/userAdmin/login.tdf via the skipjackUsername parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3418 — 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-3418 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