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

This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass

Unknown · Unknown

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

7.5HighCVSS 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 11 structured product or package states 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.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.49% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown 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 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcedropbearVendor fix publishedDebian records a fixed source-package version for this release.2022.82-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcedropbearVendor fix publishedDebian records a fixed source-package version for this release.2022.82-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcedropbearVendor fix publishedDebian records a fixed source-package version for this release.2022.82-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcedropbearVendor fix publishedDebian records a fixed source-package version for this release.2022.82-1Debian Security Tracker ↗Source updated 6 Oct 2026
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-806742 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.4
11 known affected

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

  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
  • SCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)
  • SCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)
Summary
An issue was discovered in Dropbear through 2020.81. Due to a non-RFC-compliant check of the available authentication methods in the client-side SSH code, it is possible for an SSH server to change the login process in its favor. This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass. Thus, it allows an attacker to abuse a forwarded agent for logging on to another server unnoticed.
Remediation
Update to V2.4 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-22989

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 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

An issue was discovered in Dropbear through 2020.81. Due to a non-RFC-compliant check of the available authentication methods in the client-side SSH code, it is possible for an SSH server to change the login process in its favor. This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass. Thus, it allows an attacker to abuse a forwarded agent for logging on to another server unnoticed.

What

An issue was discovered in Dropbear through 2020.81. Due to a non-RFC-compliant check of the available authentication methods in the client-side SSH code, it is possible for an SSH server to change the login process in its favor. This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass. Thus, it allows an attacker to abuse a forwarded agent for logging on to another server unnoticed.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path 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

An issue was discovered in Dropbear through 2020.81. Due to a non-RFC-compliant check of the available authentication methods in the client-side SSH code, it is possible for an SSH server to change the login process in its favor. This attack can bypass additional security measures such as FIDO2 tokens or SSH-Askpass. Thus, it allows an attacker to abuse a forwarded agent for logging on to another server unnoticed.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path 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
a network path → Improper Authentication → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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-287 ↗

CWE-287: Improper Authentication. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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

AVNetworkAttack vector: The vulnerable component can be reached over a 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.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-287
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-20221019Security Bulletin 19 Oct 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Oct 2022, published on 19 October 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

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

Siemens SSA-943925 du 13 février 2024 https://cert-portal.siemens.com/productcert/html/ssa-943925.html Référence CVE CVE-2006-20001 https://www.cve.org/CVERecord?id=CVE-2006-20001 Référence CVE CVE-2019-19135 https://www.cve.org/CVERecord?id=CVE-2019-19135 Référence CVE CVE-2020-10735 https://www.cve.org/CVERecord?id=CVE-2020-10735 Référence CVE CVE-2020-11896 https://www.cve.org/CVERecord?id=CVE-2020-11896 Référence CVE CVE-2020-1967 https://www.cve.org/CVERecord?id=CVE-2020-1967 Référence CVE CVE-2020-1971 https://www.cve.org/CVERecord?id=CVE-2020-1971 Référence CVE CVE-2021-3445 https://www.cve.org/CVERecord?id=CVE-2021-3445 Référence CVE CVE-2021-36369 https://www.cve.org/CVERecord?id=CVE-2021-36369 Référence CVE CVE-2021-3638 https://www.cve.org/CVERecord?id=CVE-2021-3638 Référence CVE CVE-2021-4037 https://www.cve.org/CVERecord?id=CVE-2021-4037 Référence CVE CVE-2021-43666 https://www.cve.org/CVERecord?id=CVE-2021-43666 Référence CVE CVE-2021-45451 https://www.cve.org/CVERecord?id=CVE-2021-45451 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-1015 https://www.cve.org/CVERecord?id=CVE-2022-1015 Référence CVE CVE-2022-1348 https://www.cve.org/CVERecord?id=CVE-2022-1348 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-020375dropbear ssh project の dropbear ssh 他複数ベンダの製品における認証に関する脆弱性

dropbear ssh project の dropbear ssh 他複数ベンダの製品には、認証に関する脆弱性が存在します。

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
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 12 Oct 2022 · Last source change 15 May 2025, 18:45 UTC · CWE-287 · Improper Authentication

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-22989
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
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. 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
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-36369 · cve.blacktree.nl