HIGH: Loop DoS Special Report

DESCRIPTION LAST UPDATED: 2023-12-20

DEFAULT SEVERITY LEVEL: HIGH

This special report contains information about hosts that can be abused in a novel type of Denial-of-Service (DoS) attacks: loop DoS. Loop DoS becomes possible if two network services indefinitely respond to each other’s messages. The hosts contained in this file have been found to cause such endless loop patterns.

To illustrate the attack vector, imagine two DNS resolvers that respond with an error message when receiving an error message as input. If an error as input creates an error as output, and a second system behaves the same, these two systems will keep sending error messages back and forth — indefinitely. The figure below shows such an example we identified among real DNS servers. An attacker can cause a loop among two faulty DNS servers by injecting a single, IP-spoofed DNS server failure message. Once injected, the servers continuously send DNS error messages back and forth, putting stress on both servers and any network link connecting them.

Loop DoS attack illustration

If you receive the report for your network, we would appreciate feedback as to the vendor/product involved. This is necessary for us to alert vendors to patch this vulnerability. You can report feedback via e-mail to loop-dos (at) shadowserver.org or simply Contact Us.

What are Shadowserver Special Reports?

Shadowserver Special Reports are unlike all of our other standard free daily network reports. They do not cover a specific daily 24 hour time period.

Instead, we send out Special Reports in situations where we are able to share one-time, high value datasets that we feel should be reported responsibly for maximum public benefit. Sometimes there are incidents when it would be useful to be able to notify potential victims about events or breaches that may have impacted them outside of the previous 24 hour period, when it may take a number of days for incident responders to conduct forensic investigations and analyzed data becomes available for sharing with potential victims. Although the events included in these Special Reports will fall outside of our usual 24 hour daily reporting window, we believe that there would still be significant benefit to our constituents in receiving and hopefully acting on the retrospective data.

If you have missed a Special Report because you were NOT yet a subscriber at the time a report was pushed out, simply subscribe for your network now and specifically request all recent Shadowserver Special Reports – and we will regenerate them specifically for your network, at no cost.

Note that the data shared across special reports may differ on a case by case basis, hence the report formats for different Special Reports may be different.

Severity levels are described here.

Filename prefix: 2023-12-19-special.

Fields

  • timestamp
    The timestamp when an event was observed (UTC+0)
  • ip
    IP address of the affected device.
  • port
    TCP or UDP port identified
  • protocol
    Protocol (UDP)
  • asn
    Autonomous System Number of the affected device
  • geo
    Country of the affected device
  • region
    Region of the affected device
  • city
    City of the affected device
  • hostname
    Hostname of the affected device (may be from reverse DNS)
  • naics
    North American Industry Classification System Code
  • sector
    Sector of the IP in question
  • tag
    Additional tags for more insight (loop-dos), including application protocol (for example, dns)
  • public_source
    Source of the data
  • status
    Status of the affected IP (compromised in this case)
  • detail
    Unused
  • method
    Unused
  • device_vendor
    Device vendor, if identified
  • device_model
    Device model, if identified
  • device_version
    Device version, if identified
  • severity
    Severity level

Sample

"timestamp","ip","port","protocol","asn","geo","region","city","hostname","naics","sector","tag","public_source","status","detail","method","device_vendor","device_type","device_model","device_version","severity"
"2010-02-10 00:00:00",192.168.0.1,53,udp,64512,ZZ,Region,City,node01.example.com,0,,dns;loop-dos,,,,,,,,,high
"2010-02-10 00:00:01",192.168.0.2,53,udp,64512,ZZ,Region,City,node02.example.com,0,,dns;loop-dos,,,,,,,,,high
"2010-02-10 00:00:02",192.168.0.3,53,udp,64512,ZZ,Region,City,node03.example.com,0,,dns;loop-dos,,,,,,,,,high

Our 126 Report Types