CVE-2024-7546
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 · uneditedoFono SimToolKit Heap-based Buffer Overflow Privilege Escalation Vulnerability. This vulnerability allows local attackers to execute arbitrary code on affected installations of oFono. An attacker must first obtain the ability to execute code on the target modem in order to exploit this vulnerability. The specific flaw exists within the parsing of STK command PDUs. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-23459.
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 · high confidenceoFono SimToolKit contains a heap-based buffer overflow vulnerability in its STK command PDU parsing logic. The flaw stems from insufficient validation of user-supplied data length before copying into heap buffers, allowing attackers with prior modem code execution to escalate privileges to the service account context.
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 data= 2.3CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify oFono installation and versionRun 'dpkg -l | grep ofono' or 'rpm -qa | grep ofono' to list installed ofono packages, or check for /usr/sbin/ofonod binary and run 'ofonod --version' if availableAffected if The installed version equals 2.3
-
Confirm STK (SimToolKit) plugin is loadedCheck /etc/ofono/plugins directory for stk.plugin, or run 'ofonod --plugins' to list loaded plugins, or inspect process list for ofonod and check /var/lib/ofono for stk-related configurationAffected if STK plugin is present and loaded by the ofonod service
-
Identify STK-enabled modem interfacesList contents of /var/lib/ofono or run 'dbus-send --system --dest=org.ofono /ril_0' to query modem interfaces, looking for STK-specific object pathsAffected if Any modem interface has STK (SimToolKit) capability enabled and accessible
-
Verify STK command processing is activeCheck if /var/lib/ofono/<modem>/stk or similar directory exists and contains active profile data, or monitor for incoming STK commands via ofono debug logs if enabledAffected if STK command processing is actively configured on any accessible modem interface
You are affected if oFono version 2.3 is installed with STK plugin loaded and any modem interface has SimToolKit capability enabled, as this creates the vulnerable STK PDU parsing code path.
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 dataApply vendor patches for oFono and ensure input length validation is enforced before heap memory operations in STK PDU parsing routines. Restrict modem interface access to reduce the prerequisite attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7546 — 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-7546 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