ID CVE-2020-25862
Summary In Wireshark 3.2.0 to 3.2.6, 3.0.0 to 3.0.13, and 2.6.0 to 2.6.20, the TCP dissector could crash. This was addressed in epan/dissectors/packet-tcp.c by changing the handling of the invalid 0xFFFF checksum.
References
Vulnerable Configurations
  • cpe:2.3:a:wireshark:wireshark:2.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.8:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.8:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.9:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.9:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.10:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.10:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.11:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.11:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.12:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.12:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.13:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.13:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.14:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.14:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.15:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.15:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.16:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.16:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:2.6.20:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:2.6.20:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:wireshark:wireshark:3.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:wireshark:wireshark:3.2.6:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 17-10-2020 - 16:15)
Impact:
Exploitability:
CWE CWE-354
CAPEC
  • Padding Oracle Crypto Attack
    An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key. Any cryptosystem can be vulnerable to padding oracle attacks if the encrypted messages are not authenticated to ensure their validity prior to decryption, and then the information about padding error is leaked to the adversary. This attack technique may be used, for instance, to break CAPTCHA systems or decrypt/modify state information stored in client side objects (e.g., hidden fields or cookies). This attack technique is a side-channel attack on the cryptosystem that uses a data leak from an improperly implemented decryption routine to completely subvert the cryptosystem. The one bit of information that tells the adversary whether a padding error during decryption has occurred, in whatever form it comes, is sufficient for the adversary to break the cryptosystem. That bit of information can come in a form of an explicit error message about a padding error, a returned blank page, or even the server taking longer to respond (a timing attack). This attack can be launched cross domain where an adversary is able to use cross-domain information leaks to get the bits of information from the padding oracle from a target system / service with which the victim is communicating. To do so an adversary sends a request containing ciphertext to the target system. Due to the browser's same origin policy, the adversary is not able to see the response directly, but can use cross-domain information leak techniques to still get the information needed (i.e., information on whether or not a padding error has occurred). For instance, this can be done using "img" tag plus the onerror()/onload() events. The adversary's JavaScript can make web browsers to load an image on the target site, and know if the image is loaded or not. This is 1-bit information needed for the padding oracle attack to work: if the image is loaded, then it is valid padding, otherwise it is not.
  • Checksum Spoofing
    An adversary spoofs a checksum message for the purpose of making a payload appear to have a valid corresponding checksum. Checksums are used to verify message integrity. They consist of some value based on the value of the message they are protecting. Hash codes are a common checksum mechanism. Both the sender and recipient are able to compute the checksum based on the contents of the message. If the message contents change between the sender and recipient, the sender and recipient will compute different checksum values. Since the sender's checksum value is transmitted with the message, the recipient would know that a modification occurred. In checksum spoofing an adversary modifies the message body and then modifies the corresponding checksum so that the recipient's checksum calculation will match the checksum (created by the adversary) in the message. This would prevent the recipient from realizing that a change occurred.
  • Manipulating Writeable Configuration Files
    Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:N/A:P
Last major update 17-10-2020 - 16:15
Published 06-10-2020 - 15:15
Last modified 17-10-2020 - 16:15
Back to Top