CVE-2004-0791 : Détail

CVE-2004-0791

26.64%V4
Network
2005-04-13
02h00 +00:00
2018-10-19
12h57 +00:00
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Multiple TCP/IP and ICMP implementations allow remote attackers to cause a denial of service (network throughput reduction for TCP connections) via a blind throughput-reduction attack using spoofed Source Quench packets, aka the "ICMP Source Quench attack." NOTE: CVE-2004-0790, CVE-2004-0791, and CVE-2004-1060 have been SPLIT based on different attacks; CVE-2005-0065, CVE-2005-0066, CVE-2005-0067, and CVE-2005-0068 are related identifiers that are SPLIT based on the underlying vulnerability. While CVE normally SPLITs based on vulnerability, the attack-based identifiers exist due to the variety and number of affected implementations and solutions that address the attacks instead of the underlying vulnerabilities.

Informations du CVE

Métriques

Métriques Score Gravité CVSS Vecteur Source
V2 5 AV:N/AC:L/Au:N/C:N/I:N/A:P nvd@nist.gov

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

Informations sur l'Exploit

Exploit Database EDB-ID : 25387

Date de publication : 2005-04-11 22h00 +00:00
Auteur : Fernando Gont
EDB Vérifié : Yes

source: https://www.securityfocus.com/bid/13124/info Multiple vendor implementations of TCP/IP Internet Control Message Protocol (ICMP) are reported prone to several denial-of-service attacks. ICMP is employed by network nodes to determine certain automatic actions to take based on network failures reported by an ICMP message. Reportedly, the RFC doesn't recommend security checks for ICMP error messages. As long as an ICMP message contains a valid source and destination IP address and port pair, it will be accepted for an associated connection. The following individual attacks are reported: - A blind connection-reset attack. This attack takes advantage of the specification that describes that on receiving a 'hard' ICMP error, the corresponding connection should be aborted. The Mitre ID CAN-2004-0790 is assigned to this issue. A remote attacker may exploit this issue to terminate target TCP connections and deny service for legitimate users. - An ICMP Source Quench attack. This attack takes advantage of the specification that a host must react to receive ICMP Source Quench messages by slowing transmission on the associated connection. The Mitre ID CAN-2004-0791 is assigned to this issue. A remote attacker may exploit this issue to degrade the performance of TCP connections and partially deny service for legitimate users. - An attack against ICMP PMTUD is reported to affect multiple vendors when they are configured to employ PMTUD. By sending a suitable forged ICMP message to a target host, an attacker may reduce the MTU for a given connection. The Mitre ID CAN-2004-1060 is assigned to this issue. A remote attacker may exploit this issue to degrade the performance of TCP connections and partially deny service for legitimate users. **Update: Microsoft platforms are also reported prone to these issues. https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/25387.tar.gz

Products Mentioned

Configuraton 0

Sun>>Solaris >> Version 9.0

    Sun>>Solaris >> Version 10.0

      Sun>>Sunos >> Version 5.7

      Sun>>Sunos >> Version 5.8

      Références

      http://www.securityfocus.com/bid/13124
      Tags : vdb-entry, x_refsource_BID
      http://www.redhat.com/support/errata/RHSA-2005-017.html
      Tags : vendor-advisory, x_refsource_REDHAT
      http://www.securityfocus.com/archive/1/428058/100/0/threaded
      Tags : vendor-advisory, x_refsource_FEDORA
      http://www.redhat.com/support/errata/RHSA-2005-016.html
      Tags : vendor-advisory, x_refsource_REDHAT
      http://www.redhat.com/support/errata/RHSA-2005-043.html
      Tags : vendor-advisory, x_refsource_REDHAT
      http://marc.info/?l=bugtraq&m=112861397904255&w=2
      Tags : vendor-advisory, x_refsource_HP
      http://marc.info/?l=bugtraq&m=112861397904255&w=2
      Tags : vendor-advisory, x_refsource_HP
      http://sunsolve.sun.com/search/document.do?assetkey=1-26-57746-1
      Tags : vendor-advisory, x_refsource_SUNALERT
      http://sunsolve.sun.com/search/document.do?assetkey=1-26-101658-1
      Tags : vendor-advisory, x_refsource_SUNALERT
      http://marc.info/?l=bugtraq&m=112861397904255&w=2
      Tags : vendor-advisory, x_refsource_HP
      http://secunia.com/advisories/18317
      Tags : third-party-advisory, x_refsource_SECUNIA
      http://www.securityfocus.com/archive/1/428028/100/0/threaded
      Tags : vendor-advisory, x_refsource_FEDORA
      http://securityreason.com/securityalert/19
      Tags : third-party-advisory, x_refsource_SREASON
      http://securityreason.com/securityalert/57
      Tags : third-party-advisory, x_refsource_SREASON