LiveActive security incident?Get immediate response
CVE Record

CVE-2024-29745: there is a possible Information Disclosure due to uninitialized data.

there is a possible Information Disclosure due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 5.5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-29745 is an Android kernel information disclosure issue caused by uninitialized data. A local attacker with low privileges could potentially read sensitive information without user interaction. CISA lists it in the Known Exploited Vulnerabilities catalog, so organizations with affected Android devices should treat remediation as time-sensitive.

Executive priority

Prioritize remediation for Android fleets because CISA KEV confirms real-world exploitation. The vulnerability is not described as remote, but confidentiality impact is high and mobile devices commonly hold sensitive business data.

Technical view

The CVE describes CWE-908 in the Android kernel: data may be exposed because memory or data is not properly initialized. CVSS 3.1 is 5.5, with local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality impact. Integrity and availability impacts are not indicated.

Likely exposure

Exposure is most relevant for managed Android devices whose vendor firmware or kernel build includes the affected component. The bundle specifically names Google Android and Android kernel, with a Pixel security bulletin reference. Device model, patch level, and vendor support status determine practical exposure.

Exploitation context

Active exploitation is supported by the CISA KEV listing. The provided description does not establish remote exploitation, privilege escalation, persistence, or public exploit availability. It indicates local information disclosure requiring existing low-privileged local access and no user interaction.

Researcher notes

Evidence in the bundle is concise and does not include root-cause detail, affected kernel versions, exploit mechanics, or forensic indicators. Treat the Pixel bulletin, CVE record, and CISA KEV entry as authoritative anchors, and validate exposure through OEM patch documentation.

Mitigation direction

  • Apply the applicable Android or Pixel security update that addresses CVE-2024-29745.
  • Prioritize devices covered by CISA KEV remediation requirements or internal high-risk groups.
  • Check OEM guidance for non-Pixel Android devices before assuming patch availability.
  • Retire or isolate unsupported devices that cannot receive the relevant security update.
  • Use MDM reporting to enforce minimum Android security patch levels.

Validation and detection

  • Inventory Android devices by model, OEM, OS version, and security patch level.
  • Confirm vendor advisories or release notes include CVE-2024-29745 remediation.
  • Verify MDM compliance policies flag devices below the required patch level.
  • Review mobile security telemetry for unusual local access patterns where available.
  • Track CISA KEV status and vendor bulletin updates for any changed guidance.
Prepared
Confidence
medium
Sources
5

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-908: 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-2024-29745 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
Medium
CVSS
5.5 (3.1)
Known Exploited
Yes
Published

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

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
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-29745Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
GoogleAndroidAndroid kernelunaffected
Weakness

CWE details

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

CWE-908 · source CWE mapping

Use of Uninitialized Resource

Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.