AndroidOperating system · Samsung

CVE-2024-34676

HIGH · 7.3 CVSS v3.1 Published 2024-11-06

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

73/100

Remediation priority · Elevated

Official description

NVD · unedited

Out-of-bounds write in parsing subtitle file in libsubextractor.so prior to SMR Nov-2024 Release 1 allows local attackers to cause memory corruption. User interaction is required for triggering this vulnerability.

Technical summary

dbcve analysis · moderate confidence

Out-of-bounds write vulnerability in libsubextractor.so subtitle file parser allows local attackers to cause memory corruption via malicious subtitle files. The vulnerability is triggered through user interaction (opening a specially crafted subtitle file).

MitigationApply the SMR Nov-2024 Release 1 patch to address the out-of-bounds write in libsubextractor.so subtitle parsing code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

AndroidOperating system

Affected:= 12.0= 13.0= 14.0

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm device is Samsung Android

Check device manufacturer and model via Settings > About Phone > Manufacturer or run 'getprop ro.product.brand' in ADB shell

Affected if Manufacturer is not Samsung or device is not running Android OS
Check Android version

Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shell

Affected if Version is 12.0, 13.0, or 14.0 exactly
Verify libsubextractor.so exists

Check for the presence of libsubextractor.so in /system/lib/ or /system/lib64/ directories using ADB: 'find /system -name libsubextractor.so'

Affected if The library file exists on the device
Identify subtitle file handling applications

Check for media player or subtitle processing apps installed, or check which apps have permission to access subtitle files in Settings > Apps

Affected if Apps capable of opening or parsing subtitle files are installed and enabled
Confirm patch status

Check the Android Security Patch Level in Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch'

Affected if Security patch level is earlier than November 2024

A Samsung Android device running version 12.0, 13.0, or 14.0 with libsubextractor.so present and no November 2024 security patch is vulnerable when processing subtitle files.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the SMR Nov-2024 Release 1 patch to address the out-of-bounds write in libsubextractor.so subtitle parsing code.

Recommended fix Moderate confidence

SMR Nov-2024 Release 1 (November 2024 Samsung Security Update)

Check the current Android security patch level on the device in Settings > About phone > Software information > Security patch level
Ensure the device is connected to Wi-Fi and has sufficient battery
Go to Settings > Software update > Download and install to check for available updates
Install the November 2024 security update (SMR Nov-2024 Release 1) or later
After installation, verify the security patch level shows November 2024 or later in Settings > About phone > Software information > Security patch level

Caveat Samsung monthly security updates are patch-level updates and typically do not introduce breaking changes; they contain only security fixes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory

Consultation3.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

17.0 hours of engineering $3,000

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-34676 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

security.samsungmobile.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34676 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-34676?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Android

Remediation

Need this fixed?

Fix this in Android 17 hrs · Moderate

Typical engagement from $3,000

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-34676 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References