CVE-2024-40239VulnerabilityPublished 8 Nov 2024Updated 13 Nov 2024

CVE-2024-40239: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

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

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

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

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Nov 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 2026-10-25.

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

To mitigate CVE-2024-40239, users and organizations should: 1) Restrict physical access to devices running the vulnerable app to trusted individuals only, minimizing opportunities for proximate attackers. 2) Monitor device usage and app access logs for unusual activity that may indicate exploitation attempts. 3) Encourage users to enable device-level security features such as strong lock screens and biometric protections beyond the app's fingerprint function. 4) Avoid leaving devices unattended in public or shared spaces. 5) Stay informed about updates from the app developer and apply patches promptly once released. 6) Consider using alternative diary or journal applications with stronger security postures until a fix is available. 7) For organizations, implement mobile device management (MDM) policies that can restrict app installations or enforce security configurations. 8) Educate users about the risks of physical device access and the importance of safeguarding biometric authentication methods. These steps go beyond generic advice by focusing on physical security, monitoring, and proactive patch management specific to this vulnerability's attack vector and impact.

Description

An incorrect access control issue in Life: Personal Diary, Journal android app 17.5.0 allows a physically proximate attacker to escalate privileges via the fingerprint authentication function.

Impact

The primary impact of CVE-2024-40239 is unauthorized access to sensitive personal data stored within the Life: Personal Diary, Journal app. This can lead to breaches of confidentiality and integrity, as attackers may read or alter private diary entries without the legitimate user's consent. For organizations, if employees use this app on corporate devices, sensitive personal information could be exposed, potentially leading to privacy violations or insider threats. The vulnerability does not affect system availability, so denial-of-service is not a concern. The requirement for physical proximity limits remote exploitation but increases risk in environments where devices are shared, lost, or stolen. The medium severity rating reflects a balance between the high impact on data confidentiality/integrity and the limited attack vector. Overall, the threat could undermine user trust in the app and expose personal or organizational information to unauthorized parties.

References

Community reviews

Loading reviews…