CVE-2022-26437
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 · uneditedIn httpclient, there is a possible out of bounds write due to uninitialized data. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WSAP00103831; Issue ID: WSAP00103831.
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 confidenceIn the httpclient library, an out-of-bounds write vulnerability exists due to uninitialized data handling. This memory corruption flaw can be exploited remotely without any user interaction or elevated privileges, potentially allowing an attacker to escalate privileges and execute arbitrary code on the affected system.
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= 2.8.1CVSS 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 Mediatek Nbiot SDK presenceSearch system firmware, device images, or software bill of materials (SBOM) for files or components associated with Mediatek Nbiot SDK. Look for directories or files containing 'mediatek', 'nbiot', or 'mtk' in the file path or metadata.Affected if Mediatek Nbiot SDK version 2.8.1 is found in the environment
-
Locate and verify httpclient library versionSearch for the httpclient library within the SDK or device filesystem. Common file names may include 'libhttpclient', 'httpclient.a', 'httpclient.so', or similar. Extract version information from library metadata, embedded strings, or associated version files.Affected if The httpclient library version is exactly 2.8.1
-
Confirm httpclient component is in useCheck configuration files, initialization code, or runtime dependencies to determine if the httpclient module is actively loaded or referenced by the application. Look for import/include statements or dynamic linking references.Affected if The httpclient library is being loaded or used by the application
-
Identify network exposure of HTTP clientReview network configuration, firewall rules, and application network bindings to determine if the HTTP client can receive external network requests. Check if the affected device has open ports or is accessible from untrusted networks.Affected if The device running the httpclient is network-accessible to untrusted parties
The environment is affected if Mediatek Nbiot SDK version 2.8.1 with the httpclient library is present and actively being used in a network-accessible environment.
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 the vendor patch WSAP00103831 by updating to the patched version of the httpclient library. If a patch is unavailable, consider isolating the affected HTTP client component or implementing network-level controls to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26437 — 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-2022-26437 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