BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-40130High confidence

In notifyTimeout of CallRedirectionProcessor, there is a possible permission bypass due to a logic error in the code

Google · Android

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-44737

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In notifyTimeout of CallRedirectionProcessor, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege and background activity launch with no additional execution privileges needed. User interaction is not needed for exploitation.

What

In notifyTimeout of CallRedirectionProcessor, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege and background activity launch with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In notifyTimeout of CallRedirectionProcessor, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege and background activity launch with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2711Android Patchday Dezember 2025: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um sich erweiterte Berechtigungen zu verschaffen, einen Denial-of-Service-Zustand auszulösen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2472Samsung Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Samsung Android ausnutzen, um möglicherweise beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu verursachen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2023-2548Google Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode auszuführen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-2539Samsung Android: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Samsung Android ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen und seine Rechte zu erweitern.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20231101Security Bulletin 01 Nov 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Nov 2023, published on 1 November 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1056Multiples vulnérabilités dans Google Android

et 16 avant le correctif du 1 décembre 2025 Résumé De multiples vulnérabilités ont été découvertes dans Google Android. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Google indique que les vulnérabilités CVE-2025-48633 et CVE-2025-48572 sont activement exploitées. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Google Android du 01 décembre 2025 https://source.android.com/docs/security/bulletin/2025-12-01?hl=fr Référence CVE CVE-2023-40130 https://www.cve.org/CVERecord?id=CVE-2023-40130 Référence CVE CVE-2024-35970 https://www.cve.org/CVERecord?id=CVE-2024-35970 Référence CVE CVE-2025-11131 https://www.cve.org/CVERecord?id=CVE-2025-11131 Référence CVE CVE-2025-11132 https://www.cve.org/CVERecord?id=CVE-2025-11132 Référence CVE CVE-2025-11133 https://www.cve.org/CVERecord?id=CVE-2025-11133 Référence CVE CVE-2025-20725 https://www.cve.org/CVERecord?id=CVE-2025-20725 Référence CVE CVE-2025-20726 https://www.cve.org/CVERecord?id=CVE-2025-20726 Référence CVE CVE-2025-20727 https://www.cve.org/CVERecord?id=CVE-2025-20727 Référence CVE CVE-2025-20730 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0811Multiples vulnérabilités dans Google Android

d?id=CVE-2023-40116 Référence CVE CVE-2023-40117 https://www.cve.org/CVERecord?id=CVE-2023-40117 Référence CVE CVE-2023-40120 https://www.cve.org/CVERecord?id=CVE-2023-40120 Référence CVE CVE-2023-40121 https://www.cve.org/CVERecord?id=CVE-2023-40121 Référence CVE CVE-2023-40123 https://www.cve.org/CVERecord?id=CVE-2023-40123 Référence CVE CVE-2023-40125 https://www.cve.org/CVERecord?id=CVE-2023-40125 Référence CVE CVE-2023-40127 https://www.cve.org/CVERecord?id=CVE-2023-40127 Référence CVE CVE-2023-40128 https://www.cve.org/CVERecord?id=CVE-2023-40128 Référence CVE CVE-2023-40129 https://www.cve.org/CVERecord?id=CVE-2023-40129 Référence CVE CVE-2023-40130 https://www.cve.org/CVERecord?id=CVE-2023-40130 Référence CVE CVE-2023-40131 https://www.cve.org/CVERecord?id=CVE-2023-40131 Référence CVE CVE-2023-40133 https://www.cve.org/CVERecord?id=CVE-2023-40133 Référence CVE CVE-2023-40134 https://www.cve.org/CVERecord?id=CVE-2023-40134 Référence CVE CVE-2023-40135 https://www.cve.org/CVERecord?id=CVE-2023-40135 Référence CVE CVE-2023-40136 https://www.cve.org/CVERecord?id=CVE-2023-40136 Référence CVE CVE-2023-40137 https://www.cve.org/CVERecord?id=CVE-2023-40137 Référence CVE CVE-2023-40138 https://www.cve.org/CVERecord?id=CVE-2023-40138 Référence CVE CVE-2023-40139 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-015386Google の Android における脆弱性

Google の Android には、不特定の脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0379Kwetsbaarheden verholpen in Google Android en Samsung Mobile

A logic error in CallRedirectionProcessor.java may allow permission bypass, while Google has patched multiple CVEs in the September 25 and October 1, 2023 Android Security Bulletins.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Android: 16, 15, 14, 13
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Oct 2023 · Last source change 17 Dec 2025, 15:57 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-44737
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-40130 · cve.blacktree.nl