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

This could lead to local escalation of privilege with no additional execution privileges needed

Unknown · Android

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

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. 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 severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.21% 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: Within 30 daysRemediation target: Within 180 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 AndroidManifest.xml of Settings, there is a possible pairing of a Bluetooth device without user's consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-194300867
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-3584

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. 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 AndroidManifest.xml of Settings, there is a possible pairing of a Bluetooth device without user's consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-194300867

What

In AndroidManifest.xml of Settings, there is a possible pairing of a Bluetooth device without user's consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-194300867

Why

The application reaches a protected operation without first confirming that the requester is authorised.

How

An attacker operating through the affected interface may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In AndroidManifest.xml of Settings, there is a possible pairing of a Bluetooth device without user's consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-9Android ID: A-194300867

Why

The application reaches a protected operation without first confirming that the requester is authorised.

How

An attacker operating through the affected interface may attempt exploitation without authentication or user interaction. 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
the affected interface → Missing Authorization → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
None: unauthenticated exploitation is possible
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: a standard category for the underlying weakness.
CWE-862 ↗

CWE-862: Missing Authorization. The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/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.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-862
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-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éférence CVE CVE-2021-0968 https://www.cve.org/CVERecord?id=CVE-2021-0968 Référence CVE CVE-2021-0970 https://www.cve.org/CVERecord?id=CVE-2021-0970 Référence CVE CVE-2021-1972 https://www.cve.org/CVERecord?id=CVE-2021-1972 Référence CVE CVE-2021-1976 https://www.cve.org/CVERecord?id=CVE-2021-1976 Référence CVE CVE-2021-29647 https://www.cve.org/CVERecord?id=CVE-2021-29647 Référence CVE CVE-2021-33909 https://www.cve.org/CVERecord?id=CVE-2021-33909 Référence CVE CVE-2021-38204 https://www.cve.org/CVERecord?id=CVE-2021-38

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

.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-0954 https://www.cve.org/CVERecord?id=CVE-2021-0954 Référence CVE CVE-2021-0955 https://www.cve.org/CVERecord?id=CVE-2021-0955 Référence CVE CVE-2021-0956 https://www.cve.org/CVERecord?id=CVE-2021-0956 Référence CVE CVE-2021-0958 https://www.cve.org/CVERecord?id=CVE-2021-0958 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-0966 https://www.cve.org/CVERecord?id=CVE-2021-0966 Référence CVE CVE-2021-0967 https://www.cve.org/CVERecord?id=CVE-2021-0967 Référence CVE CVE-2021-0968 https://www.cve.org/CVERecord?id=CVE-2021-0968 Référence CVE CVE-2021-0969 https://www.cve.org/CVERecord?id=CVE-2021-0969 Référence CVE CVE-2021-0970 https://www.cve.org/CVERecord?id=CVE-2021-0970 Référence CVE CVE-2021-0971 https://www.cve.org/CVERecord?id=CVE-2021-0971 Référence CVE CVE-2021-0973 https://www.cve.org/CVERecord?id=CVE-2021-0973 Référence CVE CVE-2021-0976 https://www.cve.org/CVERecord?id=CVE-2021-0976 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-016599Android における認証の欠如に関する脆弱性

Android には、認証の欠如に関する脆弱性が存在します。 本脆弱性は、Android ID: A-194300867 として公開されています。

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
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
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-862 · Missing Authorization

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-3584
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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 ↗

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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-3584↗Vendor CSAF · Siemens ProductCERT · 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-0965 · cve.blacktree.nl