CVE-2024-27363VulnerabilityPublished 9 Jul 2024Updated 4 Dec 2024

CVE-2024-27363: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Complexity: Low
Attack Vector: Local
Availability: High
Confidentiality: High
Integrity: None
Privileges Required: High
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor Samsung security advisories and apply firmware or software updates promptly once patches addressing CVE-2024-27363 are released. 2. Restrict high-privilege access on devices using affected Exynos processors to trusted users only, minimizing the risk of privilege escalation leading to exploitation. 3. Employ mobile device management (MDM) solutions to enforce security policies, including application whitelisting and privilege restrictions. 4. Conduct regular security audits and vulnerability assessments on mobile devices to detect signs of compromise or unauthorized access. 5. Educate users about the risks of installing untrusted applications or rooting devices, which could elevate privileges and expose the vulnerability. 6. Use encryption and secure key storage mechanisms to reduce the impact of potential information disclosure. 7. Implement network-level protections to detect and block suspicious activity originating from compromised devices. 8. Consider isolating sensitive workloads or data from devices known to use vulnerable processors until patches are applied.

Description

A vulnerability was discovered in Samsung Mobile Processor Exynos 850, Exynos 9610, Exynos 980, Exynos 1280, Exynos 1380, Exynos 1330, Exynos W920, and Exynos W930 where it does not properly check a pointer address, which can lead to a Information disclosure.

Impact

The primary impact of CVE-2024-27363 is the unauthorized disclosure of sensitive information from affected devices. This can compromise user privacy and potentially expose cryptographic keys or authentication tokens, leading to further attacks such as account takeover or device compromise. Since the vulnerability requires high privileges, the risk is elevated if an attacker already has some level of access, such as through malware or insider threat. The confidentiality breach could affect individual users, enterprises, and government agencies relying on Samsung devices for secure communications. The availability impact is rated high in the CVSS vector but the description does not explicitly mention denial of service; this might indicate potential indirect effects on availability if exploited. The vulnerability does not affect data integrity directly but could facilitate further attacks that do. Organizations with mobile workforces using Samsung devices with these processors could face data leakage risks, regulatory compliance issues, and reputational damage if exploited. The lack of known exploits reduces immediate risk but also underscores the need for proactive mitigation.

References

Community reviews

Loading reviews…