CVE-2024-47026
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 gsc_gsa_rescue of gsc_gsa.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceAn out-of-bounds read vulnerability exists in the gsc_gsa_rescue function within gsc_gsa.c due to an incorrect bounds check. This flaw allows a local attacker to read sensitive information from memory beyond the intended buffer boundaries without requiring any elevated privileges or user interaction.
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 dataall 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 if the gsc_gsa_rescue function exists in your Android environmentSearch system binaries, libraries, or firmware images for the presence of the string 'gsc_gsa_rescue' or the source file 'gsc_gsa.c' using grep or hexdump tools on extracted Android system imagesAffected if The string or file is found, indicating the vulnerable code component is present in the device firmware
-
Determine the Android version running on the deviceRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version on the deviceAffected if The device is running any version of Android, as the advisory states all versions are affected
-
Check if the device has received the latest Google security patch levelRun 'getprop ro.build.version.security_patch' to retrieve the installed security patch date, then compare it against the most recent Android Security Bulletin at https://source.android.com/docs/security/bulletinAffected if The security patch level is earlier than the month when CVE-2024-47026 was addressed, or if the vendor has not released a patch for this CVE
-
Verify if the GSA component is present on the deviceSearch for files or libraries containing 'gsc' or 'gsa' in the filename or binary content using 'find / -name '*gsc*' -o -name '*gsa*'' on an Android device with root access or examine extracted firmwareAffected if The GSA (Google Security Assistance) related components are found on the device, indicating the attack surface for this vulnerability exists
A device is affected if it contains the gsc_gsa_rescue function from gsc_gsa.c and has not received the security update that corrects the bounds check logic in that function.
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 dataThe vulnerability should be remediated by correcting the bounds check logic in the gsc_gsa_rescue function to ensure proper validation before memory access operations. Organizations using affected software should monitor vendor advisories for patches.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47026 — 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-2024-47026 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