dbcve.org
Moscad Ip Gateway FirmwareOperating system · Motorola

CVE-2015-7936

HIGH · 7.5 CVSS v3.0 Published 2015-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Cross-site request forgery (CSRF) vulnerability in Motorola Solutions MOSCAD IP Gateway allows remote attackers to hijack the authentication of administrators for requests that modify a password.

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 confidence

Cross-site request forgery (CSRF) vulnerability in Motorola Solutions MOSCAD IP Gateway allows remote attackers to hijack the authentication of administrators for requests that modify a password. An attacker can craft malicious links or pages that, when clicked by an authenticated administrator, trigger unauthorized password changes without the victim's knowledge.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) or SameSite cookie attributes for all administrative actions, particularly password modification forms. Additionally, implement referer header validation and require re-authentication for sensitive operations.

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
Moscad Ip Gateway FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the MOSCAD IP Gateway device
    Access the device's web administrative interface by navigating to its IP address. Check the device model/version information typically displayed on the login page or in the system status section.
    Affected if The device is a Motorola Solutions MOSCAD IP Gateway running any firmware version.
  2. Locate the password modification interface
    Log into the administrative panel and navigate to settings where administrator or user passwords can be changed. This is typically found under Administration, User Management, or Settings menus.
    Affected if Password change functionality exists in the web interface.
  3. Inspect password change form for anti-CSRF tokens
    View the page source (right-click > View Page Source) or use browser developer tools (F12 > Network tab) to examine the HTML form submission for the password change operation. Look for hidden input fields containing tokens (e.g., name containing 'token', 'csrf', 'nonce') or any unique identifier that changes per session.
    Affected if The password change form does NOT contain a hidden anti-CSRF token field, or the same token value can be reused across different sessions.
  4. Check for SameSite cookie attributes
    In browser developer tools, examine the cookies set by the application. Look at the Set-Cookie headers or cookie details to check for the SameSite attribute on session or authentication cookies.
    Affected if Authentication cookies do NOT have the SameSite attribute set, or it is set to None/Lax without Secure flag.
  5. Verify referer header validation
    Submit a password change request with a missing or mismatched HTTP Referer header (using a tool like Burp Suite or curl) and observe if the request is accepted or rejected.
    Affected if The password change request succeeds without proper referer header validation.

If the device is a Motorola Solutions MOSCAD IP Gateway and the administrative password change form lacks anti-CSRF tokens, SameSite cookie protections, and referer validation, the environment is affected by CVE-2015-7936.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) or SameSite cookie attributes for all administrative actions, particularly password modification forms. Additionally, implement referer header validation and require re-authentication for sensitive operations.

Fix this in Moscad Ip Gateway Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7936 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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