BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2019-2219High confidence

n/a Android: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Unknown · Android

4.7MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 4 Aug 2024

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Android and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-2019-11861

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In several functions of NotificationManagerService.java and related files, there is a possible way to record audio from the background without notification to the user due to a permission bypass. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-119041698

What

In several functions of NotificationManagerService.java and related files, there is a possible way to record audio from the background without notification to the user due to a permission bypass. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-119041698

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 several functions of NotificationManagerService.java and related files, there is a possible way to record audio from the background without notification to the user due to a permission bypass. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-119041698

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/PR:L/UI:N/S:U/C:H/I:N/A:N

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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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.
CWE-362
A

Official authority intelligence

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

CERT-FR · French · CERTFR-2021-AVI-337Multiples vulnérabilités dans Google Android

Résumé De multiples vulnérabilités ont été découvertes dans Android. Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, une exécution de code arbitraire à distance et une atteinte à la confidentialité des données. Solution 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é Android 2021-05-01 du 03 mai 2021 https://source.android.com/security/bulletin/2021-05-01 Bulletin de sécurité Pixel 2021-05-01 du 03 mai 2021 https://source.android.com/security/bulletin/pixel/2021-05-01 Référence CVE CVE-2019-2219 https://www.cve.org/CVERecord?id=CVE-2019-2219 Référence CVE CVE-2020-11254 https://www.cve.org/CVERecord?id=CVE-2020-11254 Référence CVE CVE-2020-11273 https://www.cve.org/CVERecord?id=CVE-2020-11273 Référence CVE CVE-2020-11274 https://www.cve.org/CVERecord?id=CVE-2020-11274 Référence CVE CVE-2020-11279 https://www.cve.org/CVERecord?id=CVE-2020-11279 Référence CVE CVE-2020-11284 https://www.cve.org/CVERecord?id=CVE-2020-11284 Référence CVE CVE-2020-11285 https://www.cve.org/CVERecord?id=CVE-2020-11285 Référence CVE CVE-2020-11288 https://www.cve.org/CVERecord?id=CVE-2020-11288 Référence CVE CVE-2020-11289 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2019-16275 Référence CVE CVE-2019-17666 https://www.cve.org/CVERecord?id=CVE-2019-17666 Référence CVE CVE-2019-18683 https://www.cve.org/CVERecord?id=CVE-2019-18683 Référence CVE CVE-2019-18786 https://www.cve.org/CVERecord?id=CVE-2019-18786 Référence CVE CVE-2019-19071 https://www.cve.org/CVERecord?id=CVE-2019-19071 Référence CVE CVE-2019-19526 https://www.cve.org/CVERecord?id=CVE-2019-19526 Référence CVE CVE-2019-19529 https://www.cve.org/CVERecord?id=CVE-2019-19529 Référence CVE CVE-2019-19543 https://www.cve.org/CVERecord?id=CVE-2019-19543 Référence CVE CVE-2019-19767 https://www.cve.org/CVERecord?id=CVE-2019-19767 Référence CVE CVE-2019-2219 https://www.cve.org/CVERecord?id=CVE-2019-2219 Référence CVE CVE-2019-9460 https://www.cve.org/CVERecord?id=CVE-2019-9460 Référence CVE CVE-2020-0095 https://www.cve.org/CVERecord?id=CVE-2020-0095 Référence CVE CVE-2020-0113 https://www.cve.org/CVERecord?id=CVE-2020-0113 Référence CVE CVE-2020-0114 https://www.cve.org/CVERecord?id=CVE-2020-0114 Référence CVE CVE-2020-0115 https://www.cve.org/CVERecord?id=CVE-2020-0115 Référence CVE CVE-2020-0116 https://www.cve.org/CVERecord?id=CVE-2020-0116 Référence CVE CVE-2020-0117 https://www.cve.org/CVERecord?id=CVE-2020-0117 Référence CVE CVE-2020-0118 https://www.cve.org/CVERecord?id=CVE-2020-0118 Ré

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

ecord?id=CVE-2019-10598 Référence CVE CVE-2019-10600 https://www.cve.org/CVERecord?id=CVE-2019-10600 Référence CVE CVE-2019-10601 https://www.cve.org/CVERecord?id=CVE-2019-10601 Référence CVE CVE-2019-10605 https://www.cve.org/CVERecord?id=CVE-2019-10605 Référence CVE CVE-2019-10607 https://www.cve.org/CVERecord?id=CVE-2019-10607 Référence CVE CVE-2019-15220 https://www.cve.org/CVERecord?id=CVE-2019-15220 Référence CVE CVE-2019-15239 https://www.cve.org/CVERecord?id=CVE-2019-15239 Référence CVE CVE-2019-2217 https://www.cve.org/CVERecord?id=CVE-2019-2217 Référence CVE CVE-2019-2218 https://www.cve.org/CVERecord?id=CVE-2019-2218 Référence CVE CVE-2019-2219 https://www.cve.org/CVERecord?id=CVE-2019-2219 Référence CVE CVE-2019-2220 https://www.cve.org/CVERecord?id=CVE-2019-2220 Référence CVE CVE-2019-2221 https://www.cve.org/CVERecord?id=CVE-2019-2221 Référence CVE CVE-2019-2222 https://www.cve.org/CVERecord?id=CVE-2019-2222 Référence CVE CVE-2019-2223 https://www.cve.org/CVERecord?id=CVE-2019-2223 Référence CVE CVE-2019-2224 https://www.cve.org/CVERecord?id=CVE-2019-2224 Référence CVE CVE-2019-2225 https://www.cve.org/CVERecord?id=CVE-2019-2225 Référence CVE CVE-2019-2226 https://www.cve.org/CVERecord?id=CVE-2019-2226 Référence CVE CVE-2019-2227 https://www.cve.org/CVERecord?id=CVE-2019-2227 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-012653Android における競合状態に関する脆弱性

Android には、競合状態に関する脆弱性が存在します。 本脆弱性は、Android ID: A-119041698 として公開されています。

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.
Fix not verified
Affected
Android: Android-11
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 Dec 2019 · Last source change 4 Aug 2024, 18:42 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.1
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-09-01
European sourceENISA EUVD · EUVD-2019-11861
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2019-11861 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2019-11861"}
    ENISA EUVD ↗
  2. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD ↗
  3. CVSS scoreCVSS score changed from not recorded to 4.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N).
    Before
    not recorded
    After
    4.7 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N)
    NIST NVD ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
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-2019-2219 · cve.blacktree.nl