Network Functions Virtualization InfrastructureApplication · Cisco
CVE-2018-0460
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 · uneditedA vulnerability in the REST API of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, remote attacker to read any file on an affected system. The vulnerability is due to insufficient authorization and parameter validation checks. An attacker could exploit this vulnerability by sending a malicious API request with the authentication credentials of a low-privileged user. A successful exploit could allow the attacker to read any file on the affected system.
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 path traversal vulnerability in the REST API of Cisco Enterprise NFV Infrastructure Software allows an authenticated attacker with low-privileged credentials to read arbitrary files on the affected system. The vulnerability stems from insufficient authorization checks and parameter validation in the API, enabling attackers to manipulate file path parameters to access sensitive system files outside the intended directory.
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
Network Functions Virtualization InfrastructureApplication
all 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 if NFVIS REST API is exposedDetermine if the NFVIS REST API endpoint is accessible from network locations. Check firewall rules, ACLs, or network segmentation that may allow external access to TCP ports typically used by NFVIS API (commonly 443/HTTPS).Affected if The REST API is reachable from untrusted networks without proper network filtering.
-
Verify API authentication configurationCheck whether the NFVIS REST API requires authentication for all endpoints. Confirm that anonymous or unauthenticated access is not enabled, and review the authentication mechanism in use.Affected if The API allows authenticated requests without proper authorization validation, or low-privileged accounts can access the API.
-
Determine NFVIS software versionQuery the NFVIS system for its installed version using CLI commands (such as 'show version' or 'show system information') or via the API if accessible. Compare the version against the affected range.Affected if The installed version is any release of Cisco Enterprise NFV Infrastructure Software, as all versions are affected.
-
Review API user roles and permissionsExamine the configured users and their assigned roles in NFVIS. Identify whether low-privileged accounts exist and what API permissions they have been granted.Affected if Low-privileged users have API access and the authorization layer does not properly restrict file path traversal in API requests.
Your environment is affected if the NFVIS REST API is accessible (even with authentication) and low-privileged user accounts can make API requests, since all versions of Cisco Enterprise NFV Infrastructure Software contain the path traversal vulnerability.
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 the vendor patch from Cisco. As an interim measure, restrict network access to the NFVIS REST API to trusted management networks only, and enforce strict role-based access control policies for API users.
Fix this in Network Functions Virtualization Infrastructure
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0460 — 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-2018-0460 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