CVE-2017-12709
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 Use of Hard-Coded Credentials issue was discovered in 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 device utilizes hard-coded credentials, which could allow for unauthorized local low-privileged access to the device.
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 confidenceThe affected MRD series industrial communication devices (MRD-305-DIN, MRD-315, MRD-355, MRD-455) contain hard-coded credentials embedded in the firmware. These credentials provide local low-privileged access, allowing an attacker with local access to authenticate without proper unique credentials.
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 versionsall versionsall versionsall 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 device modelAccess the device web interface, console, or use SNMP to query the device and confirm the exact model number. Look for MRD-305-DIN, MRD-315, MRD-355, or MRD-455.Affected if The device model is one of: MRD-305-DIN, MRD-315, MRD-355, or MRD-455.
-
Check firmware versionIn the device web interface, navigate to the system information or status page to view the installed firmware version. Alternatively, access the console and use commands like 'version' or check /etc/version if accessible.Affected if Any firmware version is installed. According to the advisory, all versions of the affected products contain the hard-coded credentials.
-
Verify local access methodAttempt to access the device locally via console (serial/SSH) or via the local web interface. Try to authenticate using any locally-configured user accounts.Affected if The device allows local authentication and you can gain low-privileged access without providing unique credentials.
-
Inspect firmware for embedded credentialsIf you have access to the firmware image file, extract and examine it for hard-coded username/password strings. Look for default accounts or embedded credentials in configuration files, scripts, or the binary.Affected if The firmware image contains hard-coded credentials embedded in the code or configuration.
If the device is any MRD model (MRD-305-DIN, MRD-315, MRD-355, or MRD-455) running any firmware version and allows local authentication, the environment is affected by this hard-coded credential 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 dataUpdate firmware on all affected devices to version 1.7.5.0 or later, which removes the hard-coded credentials. Change default credentials and implement unique authentication for all device accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12709 — 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-2017-12709 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