GHSA-5fm9-h728-fwpj: Trust dns server Trust-dns Vulnerable To Remote Attackers Vulnerability

MODERATE
Published
Advisory Summary

GHSA-5fm9-h728-fwpj is a MODERATE trust-dns vulnerable to remote attackers vulnerability (General Security Weakness) affecting Trust dns server libraries in the crates.io ecosystem. The issue involves trust-dns vulnerable to remote attackers causing denial-of-service (packet loops) with crafted dns packets. Remediation is available by upgrading affected packages to version 0.22.1, 0.23.0-alpha.3.

GHSA-5fm9-h728-fwpj at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5fm9-h728-fwpj
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Trust dns server
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-5fm9-h728-fwpj

To remediate this vulnerability, upgrade all affected Trust dns server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

trust-dns-server fixed: 0.22.1
Upgrade trust-dns-server to 0.22.1
trust-dns-server fixed: 0.23.0-alpha.3
Upgrade trust-dns-server to 0.23.0-alpha.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for trust-dns-server

How to Check if You Are Affected

To determine whether your application is affected by GHSA-5fm9-h728-fwpj, inspect your project dependencies for Trust dns server:

inspect dependencies for trust-dns-server

Analyze the terminal output to locate any version of Trust dns server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.22.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Trust dns server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

trust-dns and trust-dns-server are vulnerable to remotely triggered denial-of-service attacks, consuming both network and CPU resources. DNS messages with the QR=1 bit set are responded to with a `FormErr` response. This allows creating a traffic loop, in which these `FormErr` responses are sent nonstop between vulnerable servers. There are two scenarios how this can be exploited: 1) Create a loop between two instances of trust-dns, consuming network resources, or 2) consuming the CPU of a single instance. With two instances *A* and *B* an attacker sends a DNS query with a spoofed source IP address to *A*. *A* replies with a `FormErr` to *B*. Now both servers with ping-pong the message back and forth until by chance the packet is dropped in the network. Multiple spoofed packets can be sent by the attacker, increasing resource consumption. A single server can get locked up replying to itself. Same setup as above, but now *A* sends the reply to itself. The packet is sent out as fast as the CPU and network stack manage. This locks up a CPU core. Multiple packets from the attacker consume multiple CPU cores.

GHSA-5fm9-h728-fwpj Affected Trust dns server Versions

2 component(s)
Fixed Versions:
0.22.10.23.0-alpha.3
Product / Package Ecosystem Affected Versions Fixed Version
trust-dns-server
crates.io
< 0.22.1
0.22.1
trust-dns-server
crates.io
≥ 0.23.0-alpha.2
< 0.23.0-alpha.3
0.23.0-alpha.3

References

Frequently Asked Questions

What is GHSA-5fm9-h728-fwpj?
GHSA-5fm9-h728-fwpj is a security vulnerability in Trust dns server involving trust-dns vulnerable to Remote Attackers causing Denial-of-Service (packet loops) with crafted DNS packets under General Security Weakness.
Which Trust dns server versions are affected?
Affected versions include releases prior to 0.22.1, 0.23.0-alpha.3 across affected packages: trust-dns-server.
What version fixes GHSA-5fm9-h728-fwpj?
Upgrading to 0.22.1, 0.23.0-alpha.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is trust-dns-server affected?
Yes, trust-dns-server is affected in releases prior to 0.22.1, 0.23.0-alpha.3. Upgrade your dependency to 0.22.1, 0.23.0-alpha.3 or later.
What CWE is associated with GHSA-5fm9-h728-fwpj?
GHSA-5fm9-h728-fwpj is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-5fm9-h728-fwpj?
Run the dependency tree command: 'inspect dependencies for trust-dns-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5fm9-h728-fwpj",
  "modified" : "2023-06-06T02:06:23Z",
  "published" : "2023-06-06T02:06:23Z",
  "aliases" : [ ],
  "summary" : "trust-dns vulnerable to Remote Attackers causing Denial-of-Service (packet loops) with crafted DNS packets",
  "details" : "trust-dns and trust-dns-server are vulnerable to remotely triggered denial-of-service attacks, consuming both network and CPU resources.\nDNS messages with the QR=1 bit set are responded to with a `FormErr` response.\nThis allows creating a traffic loop, in which these `FormErr` responses are sent nonstop between vulnerable servers.\n\nThere are two scenarios how this can be exploited: 1) Create a loop between two instances of trust-dns, consuming network resources, or 2) consuming the CPU of a single instance.\n\nWith two instances *A* and *B* an attacker sends a DNS query with a spoofed source IP address to *A*.\n*A* replies with a `FormErr` to *B*.\nNow both servers with ping-pong the message back and forth until by chance the packet is dropped in the network.\nMultiple spoofed packets can be sent by the attacker, increasing resource consumption.\n\nA single server can get locked up replying to itself.\nSame setup as above, but now *A* sends the reply to itself.\nThe packet is sent out as fast as the CPU and network stack manage.\nThis locks up a CPU core.\nMultiple packets from the attacker consume multiple CPU cores.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "trust-dns-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.22.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "trust-dns-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.23.0-alpha.2"
      }, {
        "fixed" : "0.23.0-alpha.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bluejekyll/trust-dns/pull/1952"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bluejekyll/trust-dns"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2023-0041.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-06-06T02:06:23Z",
    "nvd_published_at" : null
  }
}