Security readout for executives and security teams
Plain-English summary
CVE-2024-37676 is a high-severity local vulnerability reported in htop v.2.20. The sources say a local attacker can cause out-of-bounds memory access in a header settings function. The business risk is highest on systems where untrusted local users or shared shell access exist. Patch and affected-package details are not provided in the bundle.
Executive priority
Treat this as a high-priority hygiene item for multi-user and administrator workstations, not as an internet-exposed emergency based on current evidence. The main uncertainty is incomplete affected-version and fix data.
Technical view
The CVE describes out-of-bounds access in htop's Header_populateFromSettings function, mapped to CWE-119 and CWE-787. CVSS 3.1 is 8.4 with local attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts. The supplied sources do not name CPEs, fixed versions, or vendor remediation.
Likely exposure
Exposure is likely limited to systems running the affected htop version where local users can execute or influence htop. The source bundle lists affected vendor/product data as n/a, so package-manager mappings and downstream distribution status need confirmation.
Exploitation context
The bundle does not show CISA KEV listing or evidence of active exploitation. It identifies a local attacker condition, but does not provide validated exploit maturity, affected platforms, or operational prerequisites beyond htop v.2.20 and the named function.
Researcher notes
Key gaps are affected CPEs, fixed commit or release, distribution backports, and independent exploit confirmation. The CVSS vector suggests severe local impact, but the public bundle only states out-of-bounds access and does not substantiate exploitability details.
Mitigation direction
Inventory systems with htop installed and record exact package versions.
Check htop project and operating-system vendor advisories for fixed packages.
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-119: 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.
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.
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
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.