CVE-2023-31116
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 · uneditedAn issue was discovered in the Shannon RCS component in Samsung Exynos Modem 5123 and 5300. An incorrect default permission can cause unintended querying of RCS capability via a crafted application.
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 confidenceThis vulnerability exists in the Shannon RCS (Rich Communication Services) component of Samsung Exynos Modems 5123 and 5300. An incorrect default permission configuration allows a malicious or crafted application to query RCS capabilities without proper authorization, potentially exposing sensitive RCS-related functionality and user 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 dataall versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the device modem modelCheck the device's modem firmware information. On most Samsung devices, dial *#197328640# or go to Settings > About Phone > Software Information > Modem Firmware. Alternatively, use ADB command: 'adb shell dumpsys telephony | grep -i modem'Affected if The modem model shows Exynos 5123 or Exynos 5300
-
Verify the modem firmware versionLocate the modem firmware version string in the same menu or ADB output. Look for version numbers typically displayed as dates or build numbers (e.g., XXXX_XXXX_XXXX)Affected if The device contains Exynos 5123 or Exynos 5300 modem firmware (all versions are affected per vendor advisory)
-
Confirm the chipset manufacturerVerify the device uses Samsung Exynos chipset. Check via Settings > About Phone > Chipset or through device specifications published by the device manufacturerAffected if The device uses Samsung Exynos modem silicon (5123 or 5300 variant)
-
Check RCS availability statusExamine whether RCS (Rich Communication Services) is provisioned on the device. This may be visible in Phone app settings under RCS, or accessible via service code *#*#726633#*#* for Samsung devices. Check carrier messaging app settingsAffected if RCS is enabled or available on the device - the vulnerable Shannon RCS component is present and queryable
A device is affected if it contains a Samsung Exynos Modem 5123 or 5300 with any firmware version, regardless of RCS enablement status, since the incorrect default permission exists in all versions.
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-supplied firmware updates from Samsung for affected Exynos Modem 5123 and 5300 devices. Monitor vendor security advisories for patch availability.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31116 — 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-31116 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