Insufficient Verification of Data Authenticity Affecting shadowsocks-rust package, versions <1.22.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-SHADOWSOCKSRUST-8719765
  • published12 Feb 2025
  • disclosed10 Feb 2025

Introduced: 10 Feb 2025

NewCVE-2025-25188  (opens in a new tab)
CWE-345  (opens in a new tab)

How to fix?

Upgrade Chainguard shadowsocks-rust to version 1.22.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadowsocks-rust package and not the shadowsocks-rust package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Hickory DNS is a Rust based DNS client, server, and resolver. A vulnerability present starting in version 0.8.0 and prior to versions 0.24.3 and 0.25.0-alpha.5 impacts Hickory DNS users relying on DNSSEC verification in the client library, stub resolver, or recursive resolver. The DNSSEC validation routines treat entire RRsets of DNSKEY records as trusted once they have established trust in only one of the DNSKEYs. As a result, if a zone includes a DNSKEY with a public key that matches a configured trust anchor, all keys in that zone will be trusted to authenticate other records in the zone. There is a second variant of this vulnerability involving DS records, where an authenticated DS record covering one DNSKEY leads to trust in signatures made by an unrelated DNSKEY in the same zone. Versions 0.24.3 and 0.25.0-alpha.5 fix the issue.