LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37789: stb_image.h 2.27 has a heap-based buffer over in stbi__jpeg_load, leading to Information Disclosure or Deni...

stb_image.h 2.27 has a heap-based buffer over in stbi__jpeg_load, leading to Information Disclosure or Denial of Service.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw is in stb_image.h’s JPEG loading path. If software processes a crafted JPEG with affected stb code, it may leak memory contents or crash. Business impact is highest for services that accept user-uploaded images, thumbnails, previews, or email/web content and process them automatically.

Executive priority

Treat as high priority for internet-facing or customer-facing image processing. The main risks are service outage and sensitive memory exposure, but the prompt sources do not prove active exploitation. Prioritize inventory first because the affected code may be embedded inside applications.

Technical view

CVE-2021-37789 is a CWE-787 heap-based buffer issue in stbi__jpeg_load in stb_image.h 2.27. The CVSS 3.1 score is 8.1: network-reachable attack vector, low complexity, no privileges, user interaction required, with high confidentiality and availability impact and no integrity impact.

Likely exposure

Exposure is likely where applications embed or package stb/libstb and parse JPEG files from untrusted sources. Because stb_image.h is often vendored as source, affected copies may not appear as normal package dependencies.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires a target application or user workflow to load attacker-controlled JPEG data with affected stb_image code. The documented outcomes are information disclosure or denial of service.

Researcher notes

Affected product metadata in the source bundle is incomplete, listing vendor and product as n/a while describing stb_image.h 2.27. Avoid assuming downstream products are affected without confirming embedded code. Debian issued DLA 3305-1 for libstb, but the bundle does not name a universal upstream fixed version.

Mitigation direction

  • Apply Debian’s libstb security update where Debian packages are used.
  • Inventory vendored stb_image.h copies and identify version 2.27 usage.
  • Check upstream stb issue guidance for the fixed or recommended version.
  • Prioritize services that process externally supplied JPEG images.
  • Consider sandboxing or isolating image parsing for exposed upload pipelines.

Validation and detection

  • Confirm whether stb_image.h 2.27 exists in source trees or bundled dependencies.
  • Map all JPEG parsing paths that accept external or user-controlled files.
  • Check production images and build artifacts for embedded libstb copies.
  • Verify Debian systems have received the referenced libstb security update.
  • Review crash or memory-disclosure telemetry around JPEG processing services.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37789 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2021-37789Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.