BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-0931High confidence

This could lead to local information disclosure with User execution privileges needed

Unknown · Android

Official source article: Siemens SSA-770721 ↗. Check the applicable product and release in the original source.

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • 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. Verify the installed build against the product-specific fixed version after deployment.
  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: As exposure requiresRemediation target: Within 365 days

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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SSA-770721 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-770721: Multiple Vulnerabilities in SIMATIC RF160B before V2.2
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC RF160B (6GT2003-0FA00)
Summary
In getAlias of BluetoothDevice.java, there is a possible way to create misleading permission dialogs due to missing data filtering. This could lead to local information disclosure with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-180747689
Remediation
Update to V2.2 or later version
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-2021-3550

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In getAlias of BluetoothDevice.java, there is a possible way to create misleading permission dialogs due to missing data filtering. This could lead to local information disclosure with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-180747689

What

In getAlias of BluetoothDevice.java, there is a possible way to create misleading permission dialogs due to missing data filtering. This could lead to local information disclosure with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-180747689

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 without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

In getAlias of BluetoothDevice.java, there is a possible way to create misleading permission dialogs due to missing data filtering. This could lead to local information disclosure with User execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-180747689

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 without authentication after a user interaction. If successful, the issue may obtain information outside the intended access boundary.

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 → obtain information outside the intended access boundary
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
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:N/UI:R/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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.
Unauthenticated
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20211222Security Bulletin 22 Dec 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Dec 2021, published on 22 December 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0203Multiples vulnérabilités dans les produits Siemens

.cve.org/CVERecord?id=CVE-2021-0706 Référence CVE CVE-2021-0708 https://www.cve.org/CVERecord?id=CVE-2021-0708 Référence CVE CVE-2021-0870 https://www.cve.org/CVERecord?id=CVE-2021-0870 Référence CVE CVE-2021-0919 https://www.cve.org/CVERecord?id=CVE-2021-0919 Référence CVE CVE-2021-0920 https://www.cve.org/CVERecord?id=CVE-2021-0920 Référence CVE CVE-2021-0926 https://www.cve.org/CVERecord?id=CVE-2021-0926 Référence CVE CVE-2021-0928 https://www.cve.org/CVERecord?id=CVE-2021-0928 Référence CVE CVE-2021-0929 https://www.cve.org/CVERecord?id=CVE-2021-0929 Référence CVE CVE-2021-0930 https://www.cve.org/CVERecord?id=CVE-2021-0930 Référence CVE CVE-2021-0931 https://www.cve.org/CVERecord?id=CVE-2021-0931 Référence CVE CVE-2021-0933 https://www.cve.org/CVERecord?id=CVE-2021-0933 Référence CVE CVE-2021-0952 https://www.cve.org/CVERecord?id=CVE-2021-0952 Référence CVE CVE-2021-0953 https://www.cve.org/CVERecord?id=CVE-2021-0953 Référence CVE CVE-2021-0961 https://www.cve.org/CVERecord?id=CVE-2021-0961 Référence CVE CVE-2021-0963 https://www.cve.org/CVERecord?id=CVE-2021-0963 Référence CVE CVE-2021-0964 https://www.cve.org/CVERecord?id=CVE-2021-0964 Référence CVE CVE-2021-0965 https://www.cve.org/CVERecord?id=CVE-2021-0965 Référence CVE CVE-2021-0967 https://www.cve.org/CVERecord?id=CVE-2021-0967 Ré

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

.cve.org/CVERecord?id=CVE-2021-0922 Référence CVE CVE-2021-0923 https://www.cve.org/CVERecord?id=CVE-2021-0923 Référence CVE CVE-2021-0924 https://www.cve.org/CVERecord?id=CVE-2021-0924 Référence CVE CVE-2021-0925 https://www.cve.org/CVERecord?id=CVE-2021-0925 Référence CVE CVE-2021-0926 https://www.cve.org/CVERecord?id=CVE-2021-0926 Référence CVE CVE-2021-0927 https://www.cve.org/CVERecord?id=CVE-2021-0927 Référence CVE CVE-2021-0928 https://www.cve.org/CVERecord?id=CVE-2021-0928 Référence CVE CVE-2021-0929 https://www.cve.org/CVERecord?id=CVE-2021-0929 Référence CVE CVE-2021-0930 https://www.cve.org/CVERecord?id=CVE-2021-0930 Référence CVE CVE-2021-0931 https://www.cve.org/CVERecord?id=CVE-2021-0931 Référence CVE CVE-2021-0932 https://www.cve.org/CVERecord?id=CVE-2021-0932 Référence CVE CVE-2021-0933 https://www.cve.org/CVERecord?id=CVE-2021-0933 Référence CVE CVE-2021-1048 https://www.cve.org/CVERecord?id=CVE-2021-1048 Référence CVE CVE-2021-1921 https://www.cve.org/CVERecord?id=CVE-2021-1921 Référence CVE CVE-2021-1924 https://www.cve.org/CVERecord?id=CVE-2021-1924 Référence CVE CVE-2021-1973 https://www.cve.org/CVERecord?id=CVE-2021-1973 Référence CVE CVE-2021-1975 https://www.cve.org/CVERecord?id=CVE-2021-1975 Référence CVE CVE-2021-1979 https://www.cve.org/CVERecord?id=CVE-2021-1979 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-016612Android における脆弱性

Android には、不特定の脆弱性が存在します。 本脆弱性は、Android ID: A-180747689 として公開されています。

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 availability varies by product
Affected
SIMATIC RF160B (6GT2003-0FA00)
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Dec 2021 · Last source change 3 Aug 2024, 15:55 UTC · CWE not yet assigned

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-08-14
European sourceENISA EUVD · EUVD-2021-3550
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification, 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. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2021-3550↗Siemens ProductCERT security advisory · Siemens SSA-770721↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-2021-0931 · cve.blacktree.nl