CVE-2015-7935
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 · uneditedMotorola Solutions MOSCAD IP Gateway allows remote attackers to read arbitrary files via unspecified vectors.
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 confidenceA path traversal vulnerability in Motorola Solutions MOSCAD IP Gateway permits unauthenticated remote attackers to read arbitrary files on the device's filesystem. The vulnerability has a CVSS base score of 7.5, indicating high confidentiality impact with network-level accessibility.
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 dataall 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Confirm MOSCAD IP Gateway presenceIdentify if Motorola Solutions MOSCAD IP Gateway hardware or software is deployed in your environment. Check network inventories, asset management systems, or physically locate the device.Affected if The device is present in your environment and running firmware.
-
Check network accessibility of the MOSCAD web interfaceDetermine if the MOSCAD IP Gateway web interface is accessible from the network. Use port scanning (e.g., nmap) to identify open HTTP/HTTPS ports typically 80, 443, 8080 on the device IP address.Affected if The web interface ports are open and reachable from network locations.
-
Verify the device is unauthenticatedAttempt to access the MOSCAD web interface without credentials. The vulnerability permits unauthenticated remote access, so no login should be required to trigger the path traversal.Affected if The web interface is accessible without authentication.
-
Test for path traversal responseSend an HTTP request with directory traversal sequences (e.g., ../../) to suspected endpoints on the MOSCAD web interface and observe the HTTP response for signs of file disclosure or directory listing.Affected if The device returns file contents or directory listings when traversing paths.
-
Assess network exposureReview firewall rules, ACLs, and network segmentation to determine if the MOSCAD IP Gateway is exposed to untrusted networks or the public internet.Affected if The device is reachable from untrusted network segments or the internet.
If the Motorola MOSCAD IP Gateway is present in your environment and its web interface is network-accessible without authentication, your environment is affected by this 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 vendor-supplied firmware patches if available; otherwise, restrict network access to the MOSCAD gateway using firewall rules or network segmentation to limit exposure to trusted hosts only.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7935 — 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-2015-7935 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