CVE-2018-5467
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 · uneditedAn Information Exposure Through Query Strings in GET Request issue was discovered in Belden Hirschmann RS, RSR, RSB, MACH100, MACH1000, MACH4000, MS, and OCTOPUS Classic Platform Switches. An information exposure through query strings vulnerability in the web interface has been identified, which may allow an attacker to impersonate a legitimate user.
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 confidenceThis is an information disclosure vulnerability in Hirschmann switch web interfaces where sensitive authentication data (likely credentials or session tokens) is transmitted in URL query strings via GET requests. Query strings are logged in server logs, browser history, and can be captured from network traffic, enabling attackers to steal credentials and impersonate legitimate users.
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 versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 device modelCheck the Hirschmann Rs20 switch model number via device label, SNMP, or web interface. Confirm it matches one of: 0900mmm2tdau, 0900nnm4tdau, 0900vvm2tdau, 1600l2l2sdau, 1600l2m2sdau, 1600l2s2sdau, 1600l2t1sdau, 1600m2m2sdau.Affected if The device is a Hirschmann Rs20 from the listed model variants.
-
Verify web interface is enabledAttempt to access the device via HTTP or HTTPS on common web ports (80, 443, or custom ports). Check device configuration for HTTP/HTTPS service status.Affected if The HTTP or HTTPS web interface is accessible and operational.
-
Inspect web server access logsReview server or management logs on the switch for entries containing GET requests with query parameters. Look for patterns like username=, password=, auth=, or token= in URL query strings.Affected if Logs contain GET request query strings with authentication-related parameter names or values.
-
Capture network traffic during loginUse a packet sniffer to capture authentication traffic when logging into the web interface. Examine HTTP GET requests to see if credentials appear in the URL after the ? symbol.Affected if Network captures show credentials or session tokens transmitted in URL query strings.
A defender is affected if they use an Hirschmann Rs20 switch from the listed models with the HTTP/HTTPS web interface enabled, and authentication data is being transmitted in URL query strings as seen in logs or network traffic.
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 dataAvoid using the HTTP/HTTPS web interface for authentication until a vendor patch is available; use alternative management protocols such as SSH or SNMP with appropriate access controls, and review server access logs for suspicious query string patterns.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5467 — 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-5467 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