Enterprise Network Virtualization SoftwareApplication · Cisco
CVE-2018-15402
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 Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an unauthenticated, remote attacker to conduct cross-site request forgery (CSRF) attacks. The vulnerability is due to improper validation of Origin headers on HTTP requests within the management interface. An attacker could exploit this vulnerability by convincing a targeted user to follow a URL to a malicious website. An exploit could allow the attacker to take actions within the software with the privileges of the targeted user or gain access to sensitive information.
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 confidenceCisco NFV Infrastructure Software contains a CSRF vulnerability in its web-based management interface due to improper validation of HTTP Origin headers. An attacker can craft malicious requests by tricking authenticated users into visiting specially crafted webpages, allowing the attacker to perform actions with the privileges of the victim's session.
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
Enterprise Network Virtualization SoftwareApplication
= nfvis-8.0= nfvis-9.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed NFVIS versionAccess the device CLI or web management interface and retrieve the software version. This is typically shown in the system information page, about section, or via CLI command such as 'show version' or 'show system information'.Affected if The installed version is nfvis-8.0 or nfvis-9.0 exactly (as indicated by '=' in the affected versions)
-
Verify web management interface is accessibleConfirm the NFV Infrastructure Software web-based management interface is enabled and reachable. This is typically accessible via HTTPS on port 443 or a custom management port.Affected if The web management interface is enabled and operational, as the CSRF vulnerability exists in this interface
-
Check for state-changing operations via HTTPIdentify if any configuration changes, administrative actions, or state-modifying operations can be performed through the web interface. These include device configuration, user management, or network setup functions.Affected if State-changing HTTP operations are available through the management interface without proper anti-CSRF protections
-
Inspect HTTP Origin header handlingThis requires verification through source code review or penetration testing to confirm whether the application validates the Origin header on POST, PUT, DELETE requests. In the affected versions, improper validation allows arbitrary Origin values.Affected if The application does not properly validate Origin headers, accepting unexpected or malicious origins on state-changing requests
You are affected if your installed Cisco NFV Infrastructure Software version is exactly nfvis-8.0 or nfvis-9.0 AND the web-based management interface is enabled and accepts state-changing HTTP requests without proper Origin header validation.
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 dataImplement strict Origin header validation on all state-changing HTTP requests in the management interface and consider adding anti-CSRF tokens and SameSite cookie attributes to prevent cross-site request forgery attacks.
Fix this in Enterprise Network Virtualization Software
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15402 — 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-15402 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