dbcve.org
AndroidOperating system · Google

CVE-2023-44126

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to after 13.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The vulnerability is that the Call management ("com.android.server.telecom") app patched by LG sends a lot of LG-owned implicit broadcasts that disclose sensitive data to all third-party apps installed on the same device. Those intents include data such as call states, durations, called numbers, contacts info, etc.

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 confidence

The LG Call management app (com.android.server.telecom) broadcasts sensitive call data including call states, durations, called numbers, and contact information via implicit intents. These broadcasts can be intercepted by any third-party application installed on the device, leading to unauthorized disclosure of confidential telecommunications data.

MitigationLG should replace implicit broadcasts with explicit broadcasts or more secure IPC mechanisms (such as bounded services with permission checks) and implement proper signature-level permissions to ensure only authorized system components can receive sensitive call data.

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
AndroidOperating system
Affected:>= 8.0, <= 13.0

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.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The version is 8.0 (Oreo), 9 (Pie), 10, 11, 12, 12L, or 13
  2. Identify if this is an LG device
    Check the device manufacturer in Settings > About Phone > Manufacturer, or run 'getprop ro.product.manufacturer' via ADB
    Affected if The device is manufactured by LG
  3. Check for LG Call management app
    Check installed apps for 'com.android.server.telecom' or LG's telecom-related app in Settings > Apps, or run 'pm list packages | grep -i telecom' via ADB
    Affected if The LG Call management app (com.android.server.telecom) is present on the device
  4. Verify third-party app installation capability
    Check if installation of apps from unknown sources is enabled in Settings > Security > Unknown sources, or check if Google Play Protect is disabled
    Affected if Users can install third-party applications on the device (the vulnerability allows any installed app to intercept the broadcasts)

The environment is affected if it is an LG device running Android 8.0 through 13.0 with the LG Call management app (com.android.server.telecom) installed, as any third-party app on such a device could intercept the sensitive call data broadcasts.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 13.0
Interim mitigation

LG should replace implicit broadcasts with explicit broadcasts or more secure IPC mechanisms (such as bounded services with permission checks) and implement proper signature-level permissions to ensure only authorized system components can receive sensitive call data.

Recommended fix Moderate confidence

Latest LG security update (October 2023 or later security patch level)

  1. Check your LG device model number (found in Settings > About Phone)
  2. Navigate to Settings > Security > Security update or Settings > Software update
  3. Check for and install the latest security patch or software update available for your device
  4. Verify the installed security patch level is at least the October 2023 patch or later, as this CVE was disclosed in late 2023
  5. If no update is available, consider contacting LG customer support for your specific model to request the security fix
Caveat Security updates typically have low risk; ensure device is charged and backup data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44126 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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