Mobility Services Engine 3365 FirmwareOperating system · Cisco
CVE-2018-0393
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 Read-Only User Effect Change vulnerability in the Policy Builder interface of Cisco Policy Suite could allow an authenticated, remote attacker to make policy changes in the Policy Builder interface. The vulnerability is due to insufficient authorization controls. An attacker could exploit this vulnerability by accessing the Policy Builder interface and modifying an HTTP request. A successful exploit could allow the attacker to make changes to existing policies. Cisco Bug IDs: CSCvi35007.
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 confidenceCisco Policy Suite Policy Builder interface has insufficient authorization controls that allow an authenticated read-only user to modify HTTP requests and bypass intended read-only restrictions, enabling unauthorized policy changes.
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
Mobility Services Engine 3365 FirmwareOperating system
= 18.0.0
Mobility Services Engine 3355 FirmwareOperating system
= 18.0.0
Mobility Services Engine 3310 FirmwareOperating system
= 18.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 the Cisco Mobility Services Engine model and firmware versionAccess the device CLI or administrative web interface and retrieve the firmware version. For CLI, use 'show version' or similar command. For web UI, check the system information or about page.Affected if The model is 3310, 3355, or 3365 AND the firmware version is exactly 18.0.0
-
Verify Policy Builder interface is enabledCheck the Cisco Policy Suite administrative interface configuration to confirm the Policy Builder web interface is accessible. This is typically found under the Policy Builder settings or service configuration.Affected if The Policy Builder interface is enabled and reachable on the network
-
Confirm read-only user accounts existReview the Cisco Policy Suite user management section to enumerate accounts with read-only permissions. Check the user role assignments in the Policy Builder or AAA configuration.Affected if There is at least one authenticated read-only user account configured in the system
-
Inspect for unauthorized policy modificationsReview policy change logs, audit trails, or policy version history within the Policy Builder interface. Look for changes made by read-only users or changes to policies that should not have been modified.Affected if Policy modifications exist that were not initiated by administrative users or that bypassed read-only restrictions
The environment is affected if running Cisco Mobility Services Engine model 3310, 3355, or 3365 with firmware version 18.0.0, with the Policy Builder interface enabled and read-only user accounts present.
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 for Cisco Bug ID CSCvi35007. Until patched, restrict network access to the Policy Builder interface to only trusted administrative personnel and monitor for unauthorized policy modifications.
Fix this in Mobility Services Engine 3365 Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0393 — 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-0393 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