Skip to content
Fencer Vulns
medium 5.9

CVE-2023-46445 json

AsyncSSH Rogue Extension Negotiation

published 2023-11-09 2 y ago modified 2026-07-08 4 mo ago also GHSA-cfc2-wr2v-gxm5 , PYSEC-2023-237 , EUVD-2023-0045

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

An issue in AsyncSSH before 2.14.1 allows attackers to control the extension info message (RFC 8308) via a man-in-the-middle attack, aka a "Rogue Extension Negotiation."

Patch / fix

  • pypi asyncssh 2.14.1
  • asyncssh_project asyncssh 2.14.1
  • python-asyncssh Debian 12 2.10.1-2+deb12u2
  • python-asyncssh Debian 14, Debian 13 2.15.0-1

debian advisories DEBIAN-CVE-2023-46445

  • python-asyncssh Ubuntu 20.04 LTS 1.12.2-1ubuntu0.2
  • python-asyncssh Ubuntu 22.04 LTS 2.5.0-1ubuntu0.1
  • python-asyncssh Ubuntu Pro 18.04 LTS 1.11.1-1ubuntu0.1~esm2
  • python-asyncssh Ubuntu Pro 24.04 LTS 2.10.1-2ubuntu0.1+esm1

ubuntu advisories UBUNTU-CVE-2023-46445

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-asyncssh openSUSE Tumbleweed 2.24.0-1.1

opensuse advisories openSUSE-SU-2026:11851-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-46445 updated cvss 5.9

python-asyncssh: Rogue Extension Negotiation

  • Red Hat Ceph Storage 6 python-asyncssh
    affected: no fix planned “Will not fix”
  • Red Hat Ceph Storage 7 python-asyncssh
    affected: no fix available
  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
OSV 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi asyncssh
<2.14.1
2.14.1

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
  • CWE-354 Improper Validation of Integrity Check Value

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.