CVE-2023-44121
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 · uneditedThe vulnerability is an intent redirection in LG ThinQ Service ("com.lge.lms2") in the "com/lge/lms/things/ui/notification/NotificationManager.java" file. This vulnerability could be exploited by a third-party app installed on an LG device by sending a broadcast with the action "com.lge.lms.things.notification.ACTION". Additionally, this vulnerability is very dangerous because LG ThinQ Service is a system app (having android:sharedUserId="android.uid.system" setting). Intent redirection in this app leads to accessing arbitrary not exported activities of absolutely all apps.
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 confidenceIntent redirection vulnerability in LG ThinQ Service (com.lge.lms2) allows third-party apps to send a broadcast with action 'com.lge.lms.things.notification.ACTION' to trigger the app into launching arbitrary unexported activities of any app on the device. Because ThinQ Service runs as a system app with android:uid.system privileges, the impact extends to accessing protected components across all installed applications.
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>= 9.0, <= 13.0CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:N/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.
-
Check if LG ThinQ Service app is installedRun 'pm list packages | grep lge.lms2' or check in Settings > Apps for package name com.lge.lms2Affected if The package com.lge.lms2 is installed on the device
-
Identify the installed version of com.lge.lms2Run 'dumpsys package com.lge.lms2 | grep versionName' or view the app info in Settings to see the versionAffected if The installed version falls within any vulnerable release of the ThinQ Service app on Android 9.0-13.0
-
Verify the Android OS versionCheck Settings > About Phone > Android version or run 'getprop ro.build.version.release'Affected if Android version is 9.0 (Pie), 10, 11, 12, 12L, or 13
-
Confirm the device is an LG modelCheck the device manufacturer via 'getprop ro.product.manufacturer' or inspect the device labelingAffected if The device is an LG phone or tablet likely to ship with the ThinQ Service system app
The user is affected if the device runs Android 9.0-13.0, is an LG device (or carries the LG ThinQ Service as a preinstalled system app), and has com.lge.lms2 installed with a version that contains the vulnerable broadcast receiver handling 'com.lge.lms.things.notification.ACTION'.
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 dataThis requires a firmware update from LG to add proper intent destination validation in NotificationManager.java, implementing explicit intent target checks and removing or securing the vulnerable broadcast receiver to prevent intent redirection attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44121 — 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-2023-44121 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