CVE Details for CVE: CVE-2020-11647
Summary
In Wireshark 3.2.0 to 3.2.2, 3.0.0 to 3.0.9, and 2.6.0 to 2.6.15, the BACapp dissector could crash. This was addressed in epan/dissectors/packet-bacapp.c by limiting the amount of recursion.
Timestamps
Last major update 21-07-2021 - 11:39
Published 10-04-2020 - 21:15
Last modified 21-07-2021 - 11:39
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: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.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:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
  • cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
    cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*
    cpe:2.3:o:opensuse:leap:15.2:*:*:*:*:*:*:*
CAPEC
Click the CAPEC title to display a description
  • Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to their advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [REF-89]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
  • Applications often need to transform data in and out of serialized data formats, such as XML and YAML, by using a data parser. It may be possible for an adversary to inject data that may have an adverse effect on the parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the parser, an adversary can cause the parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to their advantage. DoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious data payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
CWE
CVSS
Base
5.0
Impact
2.9
Exploitability
10.0
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
CVSS3
Base
7.5
Impact
3.6
Exploitability
3.9
Access
Attack ComplexityAttack vectorPrivileges RequiredScopeUser Interaction
LOW NETWORK NONE UNCHANGED NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE HIGH
VIA4 references
cvss-vector via4
AV:N/AC:L/Au:N/C:N/I:N/A:P
cvss3-vector via4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H