dbcve.org
Mrd 305 Din FirmwareOperating system · Westermo

CVE-2017-12703

HIGH · 8.8 CVSS v3.0 Published 2017-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A Cross-Site Request Forgery (CSRF) issue was discovered in Westermo MRD-305-DIN versions older than 1.7.5.0, and MRD-315, MRD-355, MRD-455 versions older than 1.7.5.0. The application does not verify whether a request was intentionally provided by the user, making it possible for an attacker to trick a user into making a malicious request to the server.

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 Westermo industrial routers (MRD-305-DIN, MRD-315, MRD-355, MRD-455) where the web interface lacks anti-CSRF token validation. An authenticated user visiting a malicious site can have their browser unknowingly send requests to the router, allowing attackers to perform configuration changes or administrative actions.

MitigationUpgrade Westermo MRD devices to firmware version 1.7.5.0 or later, which includes proper CSRF token validation. If upgrading is not immediately possible, consider network segmentation to limit exposure.

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
Mrd 305 Din FirmwareOperating system
Affected:all versions
Mrd 315 Din FirmwareOperating system
Affected:all versions
Mrd 355 Din FirmwareOperating system
Affected:all versions
Mrd 455 Din 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
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 checks

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

  1. Identify the device model
    Access the router's web interface or CLI and locate the device model information. Check if the device is a Westermo MRD-305-DIN, MRD-315, MRD-355, or MRD-455.
    Affected if The device model is one of the listed MRD models (MRD-305-DIN, MRD-315, MRD-355, or MRD-455).
  2. Check the firmware version
    In the router's web interface, navigate to the system status or about page to find the installed firmware version. Alternatively, use the CLI command 'version' or check the startup banner.
    Affected if The firmware version is any version (all versions are affected).
  3. Inspect web forms for CSRF token presence
    Log into the router's web interface and navigate to a configuration page that submits changes (such as network settings or admin password). View the page source or inspect the HTML form elements. Look for a hidden input field containing a token value, such as 'csrf_token', 'anticsrf', or 'token'.
    Affected if The HTML forms do not contain a hidden CSRF token field, or the submitted requests succeed without requiring a valid token.
  4. Verify CSRF token validation on form submission
    Use a web proxy or browser developer tools to capture a configuration form submission. Observe if the request includes a token parameter and whether the router validates it on the server side by attempting to submit the form without the token (or with an invalid token).
    Affected if The router accepts and processes configuration changes without requiring a valid CSRF token.

The device is affected if it is a Westermo MRD-305-DIN, MRD-315, MRD-355, or MRD-455 router and the web interface forms lack anti-CSRF token validation.

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

Upgrade Westermo MRD devices to firmware version 1.7.5.0 or later, which includes proper CSRF token validation. If upgrading is not immediately possible, consider network segmentation to limit exposure.

Fix this in Mrd 305 Din Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12703 — 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-2017-12703 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