Skip to content
OpenAdvisories

Weakness (CWE)

CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action

Variant Draft

The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.

How to prevent it (2 mitigations)

  1. Architecture and Design

    Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.

  2. Implementation

    Perform proper forward and reverse DNS lookups to detect DNS spoofing.

Source: MITRE CWE-350

All Critical High Medium Low Exploited only Public exploit

46 results · Feed

  • Unscored —
    CVE-2021-22884 EPSS 37%

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes …

    Node.js node nodejs nodejs Debian Ubuntu Alpine
  • Medium 5.8
    CVE-2020-11091

    Weave Net clusters susceptible to MitM attacks via IPv6 rogue router advertisements

    In Weave Net before version 2.6.3, an attacker able to run a process as root in a container is able to respond to DNS requests from the host and thereby insert themselves as a fake service. In a cluster with an IPv4 internal network, if IPv6 is not totally di…

    weaveworks weave github.com/weaveworks/weave Go
  • Unscored —
    CVE-2018-7160

    The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform rem…

    The Node.js Project Node.js nodejs nodejs Debian Ubuntu Alpine
  • Medium 5.5
    CVE-2018-1099

    DNS Rebinding in etcd

    DNS rebinding vulnerability found in etcd 3.3.1 and earlier. An attacker can control his DNS records to direct to localhost, and trick the browser into sending requests to localhost (or any other address).

    Red Hat etcd dgraph etcd Debian Ubuntu Wolfi Go
  • High 8.1
    CVE-2017-0902

    RubyGems has Origin Validation Error vulnerability

    RubyGems version 2.6.12 and earlier is vulnerable to a DNS hijacking vulnerability that allows a MITM attacker to force the RubyGems client to download and install gems from a server that the attacker controls.

    HackerOne RubyGems ruby2.3 ruby Debian Ubuntu Alpine RubyGems
  • High —
    CVE-2015-3900

    RubyGems vulnerable to DNS hijack attack

    RubyGems 2.0.x before 2.0.16, 2.2.x before 2.2.4, and 2.4.x before 2.4.7 does not validate the hostname when fetching gems or making API requests, which allows remote attackers to redirect requests to arbitrary domains via a crafted DNS SRV record, aka a "DNS…

    jruby rubygems-update Debian RubyGems