Full vulnerability report · 2023

CVE-2023-48795High confidence

n/a — Improper Validation of Integrity Check Value

Unknown · Unknown

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

5.9MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 36 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:High, raised one band.upgradedsince 14 Jul 2026

Evidence used

No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 93.55% 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.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

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

Siemens ProductCERT: 5 affected or under-investigation product states without a fixed product state in the same current advisory
Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
ABB Product Security Incident Response Team (PSIRT): 2 affected or under-investigation product states without a fixed product state in the same current advisory
Siemens ProductCERT: 19 affected or under-investigation product states without a fixed product state in the same current advisory
Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
Debian Security Tracker: 7 affected package states with no published fix

Distribution package intelligence

Release-specific package status

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

138 package states

Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 7 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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 release	Source package	Vendor state	Fixed version	Evidence
Alpine v3.23v3.23 · community	`buildah`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.34.0-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`doctl`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.102.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`filezilla`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.66.4-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`forgejo`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`gitea`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`k3s`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.29.3.1-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`libssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.10.6-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`nebula`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.8.1-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`pijul`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_beta8-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`podman`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`4.8.2-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`podman-tui`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.15.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`proftpd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.8b-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`putty`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.80-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`py3-asyncssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2.14.2-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`py3-paramiko`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.4.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · community	`tinyssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`20230101-r3`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · main	`dropbear`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2022.83-r4`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.23v3.23 · main	`libssh2`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.11.0-r1`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.23v3.23 · main	`openssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`9.6_p1-r0`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · community	`buildah`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.34.0-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`doctl`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.102.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`erlang26`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`26.2.1-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`filezilla`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.66.4-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`forgejo`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`gitea`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`k3s`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.29.3.1-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`libssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.10.6-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`nebula`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.8.1-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`pijul`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_beta8-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`podman`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`4.8.2-r1`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`podman-tui`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.15.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`proftpd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.8b-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`putty`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.80-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`py3-asyncssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2.14.2-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`py3-paramiko`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.4.0-r0`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · community	`tinyssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`20230101-r3`	Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · main	`dropbear`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2022.83-r4`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · main	`libssh2`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.11.0-r1`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · main	`openssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`9.6_p1-r0`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · community	`buildah`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.34.0-r1`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`doctl`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.102.0-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`erlang`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`26.2.1-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`filezilla`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.66.4-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`forgejo`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3.0-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`gitea`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.21.3-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`k3s`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.29.3.1-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`libssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.10.6-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`nebula`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.8.1-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`pijul`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.0.0_beta8-r1`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`podman`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`4.8.2-r1`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`podman-tui`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.15.0-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`proftpd`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.3.8b-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`putty`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`0.80-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`py3-asyncssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2.14.2-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`py3-paramiko`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`3.4.0-r0`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · community	`tinyssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`20230101-r3`	Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · main	`dropbear`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`2022.83-r4`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · main	`libssh2`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`1.11.0-r1`	Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · main	`openssh`	Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.	`9.6_p1-r0`	Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · source	`dropbear`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2022.83-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`erlang`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:25.3.2.8+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`filezilla`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.66.4-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`golang-go.crypto`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:0.17.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`jsch`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`libssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.10.6-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`libssh2`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.11.0-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`openssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:9.6p1-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`paramiko`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.4.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`php-phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.0.46-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`php-phpseclib3`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.0.35-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.22-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`proftpd-dfsg`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.8.b+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`proftpd-mod-proxy`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.9.3-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`putty`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.80-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`python-asyncssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.15.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`tinyssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`20230101-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · source	`trilead-ssh2`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`dropbear`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2022.83-1+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`erlang`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:25.2.3+dfsg-1+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`filezilla`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.63.0-1+deb12u3`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`golang-go.crypto`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`jsch`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`libssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.10.6-0+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`libssh2`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`openssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:9.2p1-2+deb12u2`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`paramiko`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`php-phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.0.42-1+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`php-phpseclib3`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.0.19-1+deb12u2`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.20-1+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`proftpd-dfsg`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.8+dfsg-4+deb12u3`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`proftpd-mod-proxy`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.9.2-1+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`putty`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.78-2+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`python-asyncssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.10.1-2+deb12u1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`tinyssh`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`trilead-ssh2`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`dropbear`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2022.83-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`erlang`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:25.3.2.8+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`filezilla`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.66.4-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`golang-go.crypto`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:0.17.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`jsch`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`libssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.10.6-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`libssh2`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.11.0-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`openssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:9.6p1-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`paramiko`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.4.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`php-phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.0.46-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`php-phpseclib3`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.0.35-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`proftpd-dfsg`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.8.b+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`proftpd-mod-proxy`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.9.3-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`putty`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.80-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`python-asyncssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.15.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`tinyssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`20230101-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`trilead-ssh2`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`dropbear`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2022.83-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`erlang`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:25.3.2.8+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`filezilla`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.66.4-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`golang-go.crypto`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:0.17.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`jsch`	Not affectedDebian marks this release not affected (fixed-version marker 0).	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`libssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.10.6-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`libssh2`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.11.0-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`openssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1:9.6p1-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`paramiko`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.4.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`php-phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.0.46-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`php-phpseclib3`	Vendor fix publishedDebian records a fixed source-package version for this release.	`3.0.35-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`phpseclib`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.0.22-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`proftpd-dfsg`	Vendor fix publishedDebian records a fixed source-package version for this release.	`1.3.8.b+dfsg-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`proftpd-mod-proxy`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.9.3-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`putty`	Vendor fix publishedDebian records a fixed source-package version for this release.	`0.80-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`python-asyncssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.15.0-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`tinyssh`	Vendor fix publishedDebian records a fixed source-package version for this release.	`20230101-4`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`trilead-ssh2`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-apps	`golang-go.crypto`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`dropbear`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`filezilla`	Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.	`3.66.4-1`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`openssh`	Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.	`1:9.6p1-3ubuntu1`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`openssh-ssh1`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`paramiko`	Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.	`2.12.0-2ubuntu4`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`putty`	Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`python-asyncssh`	Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.	`2.10.1-2ubuntu0.1`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and package	Affected range	First fixed version	Evidence
gogolang.org/x/crypto	`>= 0.1.0, < 0.17.0`	`0.17.0`	GitHub advisory ↗upstream repository advisory · 13 May 2026
gogolang.org/x/crypto	`< 0.0.0-20231218163308-9d2ee975ef9f`	`0.0.0-20231218163308-9d2ee975ef9f`	GitHub advisory ↗upstream repository advisory · 13 May 2026
pipparamiko	`>= 2.5.0, < 3.4.0`	`3.4.0`	GitHub advisory ↗upstream repository advisory · 13 May 2026
rustrussh	`< 0.40.2`	`0.40.2`	GitHub advisory ↗upstream repository advisory · 13 May 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.

12 current

CVE-2023-48795 · CSAF 2.0 · revision 119 · interimSUSE Product Security TeamCVE-2023-48795

228 known affected

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

apache-sshd as component of SUSE Linux Enterprise Desktop 15 SP4
libssh as component of SUSE Linux Enterprise Desktop 15 SP4
libssh-config as component of SUSE Linux Enterprise Desktop 15 SP4
libssh-devel as component of SUSE Linux Enterprise Desktop 15 SP4
libssh4 as component of SUSE Linux Enterprise Desktop 15 SP4
libssh4-32bit as component of SUSE Linux Enterprise Desktop 15 SP4
python-paramiko as component of SUSE Linux Enterprise Desktop 15 SP4
python-paramiko-doc as component of SUSE Linux Enterprise Desktop 15 SP4
python311-paramiko as component of SUSE Linux Enterprise Desktop 15 SP4
openssh as component of SUSE Linux Enterprise High Performance Computing 12 SP2
openssh-fips as component of SUSE Linux Enterprise High Performance Computing 12 SP2
openssh-helpers as component of SUSE Linux Enterprise High Performance Computing 12 SP2

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5

5 known affected

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

SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation: Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

HPESBNW04678 · CSAF 2.0 · revision 4 · finalHPE Aruba NetworkingBuffer Overflow Vulnerability Allows Arbitrary Code Execution in InstantOS OpenSSH ("TerraPin" attack)

2 known affected

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

AOS-8 Instant and AOS 10 AP
AOS-10 AP

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. The impact of this vulnerability on HPE Aruba Networking Access Points has not been confirmed, but the version of OpenSSH in InstantOS and ArubaOS 10.x software has been upgraded for mitigation.
Remediation: Upgrade HPE Aruba Networking AOS-10 AP and AOS-8 InstantOS to one of the following software versions (as applicable) to resolve this vulnerability: - AOS-10 AP 10.8.x.x: 10.8.0.0 and above - AOS-8 Instant 8.13.x.x: 8.13.0.0 and above

SSA-364175 · CSAF 2.0 · revision 8 · finalSiemens ProductCERTSSA-364175: Multiple Vulnerabilities in Palo Alto Networks Virtual NGFW on RUGGEDCOM APE1808 Devices Before V11.1.4-h1

1 known affected

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

RUGGEDCOM APE1808

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust; and there could be effects on Bitvise SSH through 9.31.
Remediation: Upgrade Palo Alto Networks Virtual NGFW V11.1.4-h1. Contact customer support to receive patch and update information

SCA-2025-0011 · CSAF 2.0 · revision 1.0.0 · finalSICK PSIRTVulnerabilities affecting Endress+Hauser SSG-E210GC

1 known not affected

The vendor explicitly states that these products are not affected by this CVE.

Endress+Hauser SSG-E210GC all Firmware versions

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation: No remediation text is recorded.

SCA-2025-0009 · CSAF 2.0 · revision 1 · finalSICK PSIRTVulnerabilities affecting SICK TDC-E210GC

1 known not affected

The vendor explicitly states that these products are not affected by this CVE.

SICK TDC-E210GC all Firmware versions

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation: No remediation text is recorded.

2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2023-48795

2 known affected

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

ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3
ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3

Summary: Remote attackers may bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack.
Remediation: Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).

SSA-769027 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-769027: Multiple Vulnerabilities fixed in SCALANCE W700 IEEE 802.11ax devices before V3.0.0

19 known affected

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

SCALANCE WAB762-1 (6GK5762-1AJ00-6AA0)
SCALANCE WAM763-1 (6GK5763-1AL00-7DA0)
SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0)
SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0)
SCALANCE WAM766-1 (6GK5766-1GE00-7DA0)
SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0)
SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0)
SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0)
SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0)
SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0)
SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0)
SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0)

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust; and there could be effects on Bitvise SSH through 9.31.
Remediation: Update to V3.0.0 or later version

SSA-915275 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 3

1 known affected

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

SINEC INS

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust; and there could be effects on Bitvise SSH through 9.31.
Remediation: Update to V1.0 SP2 Update 3 or later version

ARUBA-PSA-2024-007 · CSAF 2.0 · revision 1 · finalHPE Aruba NetworkingTerrapin Attack Vulnerability in OpenSSH Impacting AirWave Management Platform

1 known affected

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

Aruba Airwave Management Platform

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. The impact of this vulnerability on AirWave Management Platform has not been confirmed, but the version of OpenSSH has been upgraded. HPE Aruba Networking is not aware of any malicious exploitation of this vulnerability.
Remediation: To resolve the vulnerabilities described above, it is recommended to upgrade the software to the following version: HPE Aruba Networking AirWave Management Platform - 8.3.0.3 and above IMPORTANT: AirWave 8.2.15.2 is the last version based on CentOS 7 operating system. The End of Life date for CentOS 7 is set to 30-June-2024. HPE Aruba Networking recommends upgrading to AirWave 8.3.0.3, a RHEL-based AirWave version, to receive continued support for product and security updates. Refer to AirWave 8.3.0.3 Release Notes for minimum requirements, upgrade paths and detailed upgrade instructions. Software versions with resolution/fixes for the vulnerabilities covered above, can be downloaded from the HPE Networking Support Portal.

SSA-794697 · CSAF 2.0 · revision 9 · interimSiemens ProductCERTSSA-794697: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP before V1.1

1 known affected

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

SIMATIC S7-1500 TM MFP - GNU/Linux subsystem

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust; and there could be effects on Bitvise SSH through 9.31.
Remediation: Update to V1.1 or later version

ARUBA-PSA-2024-005 · CSAF 2.0 · revision 2 · finalHPE Aruba NetworkingTerrapin Attack Vulnerability in OpenSSH Impacting AOS-CX Switches

1 known affected

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

AOS-CX

Summary: The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers.
Remediation: Upgrade affected switches to one of the following AOS-CX branches and versions to resolve all the vulnerabilities described in the details section: - AOS-CX 10.13.xxxx: 10.13.1010 and above. - AOS-CX 10.12.xxxx: 10.12.1030 and above. - AOS-CX 10.10.xxxx: 10.10.1110 and above. HPE Aruba Networking does not evaluate or patch product versions that have reached their End of Maintenance (EoM) milestone. For more information about HPE Aruba's End of Support policy visit: https://www.arubanetworks.com/support-services/end-of-life/ Supported branches as of the publication date of this advisory are: - AOS-CX 10.13.xxxx - AOS-CX 10.12.xxxx - AOS-CX 10.10.xxxx Software versions with resolution/fixes for the vulnerabilities covered above, can be downloaded from the HPE Networking Support Portal.

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

What

Why

The product does not validate or incorrectly validates the integrity check values or checksums of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.

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

Why

How

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.

Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path: a network path → Improper Validation of Integrity Check Value → 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: 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-354 ↗
CWE-354: Improper Validation of Integrity Check Value. The product does not validate or incorrectly validates the integrity check values or checksums of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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: 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.

NetworkUnauthenticatedCWE-354Public exploit reference

Official authority intelligence

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

ENISA EUVD · EUVD-2023-3093Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-1032IBM Tivoli Network Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Tivoli Network Manager ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

n/a — Improper Validation of Integrity Check Value

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

EUVD-2023-3093

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance