CVE-2018-25236
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 · uneditedHirschmann HiOS and HiSecOS products RSP, RSPE, RSPS, RSPL, MSP, EES, EESX, GRS, OS, RED, EAGLE contain an authentication bypass vulnerability in the HTTP(S) management module that allows unauthenticated remote attackers to gain administrative access by crafting specially formed HTTP requests. Attackers can exploit improper authentication handling to obtain the authentication status and privileges of a previously authenticated user without providing valid credentials.
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 confidenceHirschmann HiOS and HiSecOS network switches contain an authentication bypass vulnerability in their HTTP(S) management interface. The flaw allows unauthenticated attackers to craft specially formed HTTP requests that improperly handle authentication, enabling them to obtain administrative privileges without providing valid credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device console or web interface and retrieve the system information or firmware version. This is typically found in the web UI under 'System', 'Device Info', or via CLI command 'show version'.Affected if The device is a Hirschmann product running HiOS or HiSecOS firmware and the version matches the affected range for this CVE.
-
Confirm product is HiOS or HiSecOSVerify the exact operating system name displayed in the device information page or boot logs. Look for 'HiOS' or 'HiSecOS' as the installed firmware type.Affected if The device runs HiOS or HiSecOS firmware.
-
Verify HTTP(S) management interface is enabledCheck the device configuration for web-based management settings. In the CLI, use commands like 'show web' or 'show http' or 'show https' to confirm the management interface status.Affected if The HTTP and/or HTTPS management interface is enabled on the device.
-
Assess network exposure of management interfaceDetermine if the HTTP(S) management port (typically 80 or 443) is reachable from untrusted networks. Review firewall rules, VLAN assignments, and interface IP configurations to identify exposure scope.Affected if The management interface is accessible from networks other than a trusted management VLAN or trusted IP range.
A user is affected if the device is a Hirschmann HiOS or HiSecOS system with the HTTP(S) management interface enabled and accessible, running a firmware version that falls within the affected range for this authentication bypass 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 patches or firmware updates for affected HiOS/HiSecOS devices; if patches are unavailable, restrict management interface access to trusted networks or IP addresses using firewall rules or access control lists.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25236 — 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-25236 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