CVE-2015-5367
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 · uneditedThe HP lt4112 LTE/HSPA+ Gobi 4G module with firmware before 12.500.00.15.1803 on EliteBook, ElitePad, Elite, ProBook, Spectre, ZBook, and mt41 Thin Client devices allows local users to gain privileges via unspecified vectors.
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 confidenceLocal privilege escalation vulnerability in HP lt4112 LTE/HSPA+ Gobi 4G module firmware versions prior to 12.500.00.15.1803 on HP business devices (EliteBook, ElitePad, Elite, ProBook, Spectre, ZBook, mt41 Thin Client). The vulnerability allows local users to gain elevated privileges through unspecified attack vectors.
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= 12.500.00.15.1802= 12.500.00.15.1802all 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
- Local
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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.
-
Confirm HP lt4112 Gobi 4G module is presentCheck system hardware inventory or device manager for HP lt4112 LTE/HSPA+ Gobi 4G module. On Windows, run 'wmic product get name,version' or check HP Hardware Diagnostics.Affected if The system has an HP lt4112 LTE/HSPA+ Gobi 4G module installed
-
Retrieve module firmware versionAccess the module firmware information through HP support tools, BIOS/UEFI diagnostics, or the Gobi firmware utility. The firmware version is typically shown in the module properties.Affected if Firmware version cannot be determined or shows as 12.500.00.15.1802 or earlier
-
Compare against affected version rangesDocument the exact firmware version string and compare to: versions prior to 12.500.00.15.1803 are vulnerable. Products listed as 'all versions' are affected regardless of firmware version.Affected if Version is 12.500.00.15.1802 or lower, or the product model is listed with 'all versions' in the affected products list
-
Verify system model is an affected HP business deviceCheck system information (msinfo32 or 'systeminfo' command) to confirm the HP model is one of: EliteBook, ElitePad, Elite, ProBook, Spectre, ZBook, or mt41 Thin Client.Affected if The device is an HP business model from the affected product list AND contains the vulnerable module
A system is affected if it has an HP lt4112 LTE/HSPA+ Gobi 4G module with firmware version 12.500.00.15.1802 or earlier, or if the product model is listed with 'all versions' in the affected products regardless of firmware version.
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 the lt4112 Gobi 4G module firmware to version 12.500.00.15.1803 or later. Since this is a hardware firmware issue, each affected device requires the firmware update applied directly to the module.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5367 — 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-2015-5367 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