CVE-2018-7100
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 potential security vulnerability has been identified in HPE OfficeConnect 1810 Switch Series (HP 1810-24G - P.2.22 and previous versions, HP 1810-48G PK.1.34 and previous versions, HP 1810-8 v2 P.2.22 and previous versions). The vulnerability could allow local disclosure of sensitive information.
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 confidenceA local information disclosure vulnerability exists in HPE OfficeConnect 1810 Switch Series (models 1810-24G, 1810-48G, and 1810-8 v2) affecting specified firmware versions. The vulnerability allows a locally authenticated attacker to access sensitive information. The specific mechanism and nature of the disclosed information are not detailed in the available description.
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<= p.2.22<= pk.1.34<= p.2.22CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the switch modelLocate the model number on the device physical label or in the management interface. Confirm it is one of: 1810-24G, 1810-48G, or 1810-8 V2.Affected if The model is not one of the three affected models listed.
-
Check the installed firmware versionAccess the switch CLI or web management interface and retrieve the firmware version. In CLI, this is typically shown via 'show version' or 'show system-information' commands. In the web interface, check the device status or firmware information page.Affected if Unable to retrieve the firmware version from the device.
-
Compare version against affected rangesMatch your identified model to its affected version threshold: 1810-24G at p.2.22 or below; 1810-48G at pk.1.34 or below; 1810-8 V2 at p.2.22 or below. Note that the version numbering scheme differs between models (p.x.x vs pk.x.x).Affected if The installed firmware version is at or below the threshold for your specific model.
-
Verify local access existsSince this is a local information disclosure vulnerability, determine whether untrusted individuals could gain physical access to the device or local network access to the management interface.Affected if The device is accessible to untrusted local users.
You are affected if you have an HPE OfficeConnect 1810 switch model 1810-24G, 1810-48G, or 1810-8 V2 running firmware at or below p.2.22 (or pk.1.34 for the 48G model) and untrusted local users can access the device.
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 dataLimit physical and local access to affected switches to trusted administrators only; contact HPE for patched firmware versions.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7100 — 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-7100 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