CVE-2025-22869

Published Feb 26, 2025

Last updated a year ago

CVSS high 7.5
SSH
Splunk
Tunneling protocol
Port (22)

Overview

Description
SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.
Source
security@golang.org
NVD status
Analyzed
Products
ssh

Risk scores

CVSS 3.1

Type
Secondary
Base score
7.5
Impact score
3.6
Exploitability score
3.9
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Severity
HIGH

Weaknesses

134c704f-9b21-4f2e-91b3-4a467353bcc0
CWE-770

Social media

Hype score
Not currently trending
  1. 🔴 CoreDNS, TSIG Authentication Bypass, #CVE-2025-22869 (Critical) https://t.co/TpktjLXzjc

    @dailycve

    29 Apr 2026

    91 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. 昨日の #fukuokago の資料です。「x/crypto/ssh」に存在した脆弱性(CVE-2025-22869)を発見・報告し、CVEを取得した事例を紹介しました。 https://t.co/aDDfijOPeg

    @vvvatanabe

    26 Aug 2025

    1320 Impressions

    7 Retweets

    16 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  3. ⚠️Múltiples vulnerabilidades en Dell PowerProtect ❗CVE-2025-27363 ❗CVE-2025-24855 ❗CVE-2025-27220 ❗CVE-2025-22869 ➡️Más info: https://t.co/SNJivvTJCI https://t.co/N230rAhUAG

    @CERTpy

    1 Jul 2025

    161 Impressions

    0 Retweets

    0 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  4. ALAS-2025-1982 (important): amazon-ssm-agent #CVE-2025-22869 #AWS https://t.co/rvHjxUEPP1

    @WhatsNewWithAWS

    27 Jun 2025

    46 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. ⚠️Múltiples vulnerabilidades del kernel de Linux Red Hat ❗CVE-2025-46337 ❗CVE-2025-21927 ❗CVE-2025-22869 ❗CVE-2025-30204 ❗CVE-2025-24209 ➡️Más info: https://t.co/T4ViIi50N9 https://t.co/rpOVorctqA

    @CERTpy

    2 May 2025

    79 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. 🚨 CVE-2025-22869 🔴 HIGH (7.5) 🏢 https://t.co/YfJ3ISAjvH - https://t.co/Bl7CFePxUQ 🏗️ 0 🔗 https://t.co/q9Z2nysDmv 🔗 https://t.co/aKBDtXI3CH 🔗 https://t.co/P7bl4obYSI #CyberCron #VulnAlert @golang https://t.co/mE5uD5W5RW

    @cybercronai

    27 Feb 2025

    13 Impressions

    1 Retweet

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  7. CVE-2025-22869 SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, c… https://t.co/hd6ScYOunn

    @CVEnew

    26 Feb 2025

    73 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. Zephyr's WireGuard VPN data-plane receive handler wg_process_data_message() in subsys/net/lib/wireguard/wg_crypto.c validated the anti-replay counter too late. After AEAD decryption of a MESSAGE_TRANSPORT_DATA packet succeeded, the code committed several peer-state changes — update_peer_addr() (endpoint roaming update), the keypair->last_rx/peer->last_rx liveness timers, and keypair_update() (promote next→current and destroy the previous keypair) — and only afterward called wg_check_replay(). On a replayed packet the replay check returned -EINVAL, but none of the preceding mutations were rolled back. The AEAD tag authenticates content but not freshness, so a replayed-but-authentic transport packet decrypts correctly. An attacker who captures one valid ciphertext off the wire (an on-path or shared-medium observer) can re-inject it from an arbitrary spoofed source address. Reaching the handler requires no credentials: it is driven directly from inbound UDP datagrams via the dispatch in subsys/net/lib/wireguard/wg.c. Because the state mutations committed before the replay check, the replay repoints the peer endpoint to the attacker-chosen source address (roaming hijack), redirecting the victim's subsequent outbound tunnel traffic until the legitimate peer's next packet re-corrects it; it also prematurely destroys the previous keypair and refreshes the RX liveness timer. The tunnel payload stays encrypted under the session keypair, so this is an integrity/availability impact (traffic redirection and session disruption), not payload disclosure. The fix moves wg_check_replay() to immediately after a successful decrypt, before any peer-state mutation, matching the WireGuard specification and the Linux reference implementation.CVE-2026-13734