Skip to main content

Test Results

garciapl/intercom

Vulnerabilities

 22 via 72 paths

Dependencies

 27

Source

 GitHub

Commit

 222f02b5

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 6
  • 10
  • 6
Status
  • 22
  • 0
  • 0

high severity

Denial of Service (DoS)

  • Vulnerable module: com.fasterxml.jackson.core:jackson-core
  • Introduced through: com.fasterxml.jackson.core:jackson-core@2.12.1 and com.fasterxml.jackson.core:jackson-databind@2.12.1

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-core@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-databind@2.12.1 › com.fasterxml.jackson.core:jackson-core@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.15.0.

Overview

com.fasterxml.jackson.core:jackson-core is a Core Jackson abstractions, basic JSON streaming API implementation

Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing input size validation when performing numeric type conversions. A remote attacker can exploit this vulnerability by causing the application to deserialize data containing certain numeric types with large values, causing the application to exhaust all available resources.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade com.fasterxml.jackson.core:jackson-core to version 2.15.0-rc1 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Insecure Temporary File

  • Vulnerable module: org.springframework.boot:spring-boot
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.2.11.RELEASE.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.2.11.RELEASE.

Overview

Affected versions of this package are vulnerable to Insecure Temporary File via the org.springframework.boot.web.server.AbstractConfigurableWebServerFactory.createTempDir method, allowing for temporary directory hijacking and privilege escalation.

Remediation

Upgrade org.springframework.boot:spring-boot to version 2.2.11.RELEASE or higher.

References

Insecure Temporary File vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: com.fasterxml.jackson.core:jackson-databind
  • Introduced through: com.fasterxml.jackson.core:jackson-databind@2.12.1

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-databind@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.6.1.

Overview

com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.

Affected versions of this package are vulnerable to Denial of Service (DoS) via a large depth of nested objects.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.6.1, 2.13.2.1 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: org.springframework.boot:spring-boot-autoconfigure
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.5.15.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) if Spring MVC is used together with a reverse proxy cache.

Specifically, an application is vulnerable if all of the conditions are true:

  • The application has Spring MVC auto-configuration enabled. This is the case by default if Spring MVC is on the classpath.
  • The application uses Spring Boot's welcome page support, either static or templated.
  • The application is deployed behind a proxy which caches 404 responses.

The application is NOT vulnerable if any of the following are true:

  • Spring MVC auto-configuration is disabled. This is true if WebMvcAutoConfiguration is explicitly excluded, if Spring MVC is not on the classpath, or if spring.main.web-application-type is set to a value other than SERVLET.
  • The application does not use Spring Boot's welcome page support.
  • There is no proxy which caches 404 responses.

Workaround

Users who are unable to upgrade should configure the reverse proxy not to cache 404 responses and/or not to cache responses to requests to the root (/) of the application.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade org.springframework.boot:spring-boot-autoconfigure to version 2.5.15, 2.6.15, 2.7.12, 3.0.7 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing nested depth limitation for collections.

NOTE: This vulnerability has also been identified as: CVE-2022-38749

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade org.yaml:snakeyaml to version 1.31 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Denial of Service (DoS) due to missing nested depth limitation for collections.

NOTE: This vulnerability has also been identified as: CVE-2022-25857

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade org.yaml:snakeyaml to version 1.31 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Arbitrary Code Execution

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.2.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Arbitrary Code Execution in the Constructor class, which does not restrict which types can be deserialized. This vulnerability is exploitable by an attacker who provides a malicious YAML file for deserialization, which circumvents the SafeConstructor class.

The maintainers of the library contend that the application's trust would already have had to be compromised or established and therefore dispute the risk associated with this issue on the basis that there is a high bar for exploitation.

Remediation

Upgrade org.yaml:snakeyaml to version 2.0 or higher.

References

Arbitrary Code Execution vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: com.fasterxml.jackson.core:jackson-databind
  • Introduced through: com.fasterxml.jackson.core:jackson-databind@2.12.1

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-databind@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.6.

Overview

com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.

Affected versions of this package are vulnerable to Denial of Service (DoS) when using JDK serialization to serialize and deserialize JsonNode values. It is possible for the attacker to send a 4-byte length payload, with a value of Integer.MAX_VALUE , that will eventually cause large buffer allocation and out of heap memory.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.13.1, 2.12.6 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: com.fasterxml.jackson.core:jackson-databind
  • Introduced through: com.fasterxml.jackson.core:jackson-databind@2.12.1

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-databind@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.7.1.

Overview

com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.

Affected versions of this package are vulnerable to Denial of Service (DoS) in the _deserializeFromArray() function in BeanDeserializer, due to resource exhaustion when processing a deeply nested array.

NOTE: For this vulnerability to be exploitable the non-default DeserializationFeature must be enabled.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.7.1, 2.13.4 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: com.fasterxml.jackson.core:jackson-databind
  • Introduced through: com.fasterxml.jackson.core:jackson-databind@2.12.1

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.fasterxml.jackson.core:jackson-databind@2.12.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.12.7.1.

Overview

com.fasterxml.jackson.core:jackson-databind is a library which contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor.

Affected versions of this package are vulnerable to Denial of Service (DoS) in the _deserializeWrappedValue() function in StdDeserializer.java, due to resource exhaustion when processing deeply nested arrays.

NOTE: This vulnerability is only exploitable when the non-default UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.12.7.1, 2.13.4.1 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Deserialization of Untrusted Data

  • Vulnerable module: com.google.guava:guava
  • Introduced through: com.google.guava:guava@21.0

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.google.guava:guava@21.0
    Remediation: Upgrade to com.google.guava:guava@24.1.1-android.

Overview

com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. During deserialization, two Guava classes accept a caller-specified size parameter and eagerly allocate an array of that size:

  • AtomicDoubleArray (when serialized with Java serialization)
  • CompoundOrdering (when serialized with GWT serialization)

An attacker may be able to send a specially crafted request which with then cause the server to allocate all it's memory, without validation whether the data size is reasonable.

Details

Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.

Deserialization of untrusted data (CWE-502), is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, letting the attacker to control the state or the flow of the execution.

Java deserialization issues have been known for years. However, interest in the issue intensified greatly in 2015, when classes that could be abused to achieve remote code execution were found in a popular library (Apache Commons Collection). These classes were used in zero-days affecting IBM WebSphere, Oracle WebLogic and many other products.

An attacker just needs to identify a piece of software that has both a vulnerable class on its path, and performs deserialization on untrusted data. Then all they need to do is send the payload into the deserializer, getting the command executed.

Developers put too much trust in Java Object Serialization. Some even de-serialize objects pre-authentication. When deserializing an Object in Java you typically cast it to an expected type, and therefore Java's strict type system will ensure you only get valid object trees. Unfortunately, by the time the type checking happens, platform code has already created and executed significant logic. So, before the final type is checked a lot of code is executed from the readObject() methods of various objects, all of which is out of the developer's control. By combining the readObject() methods of various classes which are available on the classpath of the vulnerable application, an attacker can execute functions (including calling Runtime.exec() to execute local OS commands).

Remediation

Upgrade com.google.guava:guava to version 24.1.1, 24.1.1-jre or higher.

References

Deserialization of Untrusted Data vulnerability report

medium severity

Multipart Content Pollution

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@1.5.10.RELEASE.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@1.5.10.RELEASE.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@1.5.10.RELEASE.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE

…and 10 more

Overview

org.springframework:spring-core is a core package within the spring-framework that contains multiple classes and utilities.

Affected versions of this package are vulnerable to Multipart Content Pollution. It provides client-side support for multipart requests. When the server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.

Remediation

Upgrade org.springframework:spring-core to version 4.3.14.RELEASE, 5.0.5.RELEASE or higher.

References

Multipart Content Pollution vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.3.0.RELEASE.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Denial of Service (DoS). The Alias feature in SnakeYAML 1.18 allows entity expansion during a load operation, a related issue to CVE-2003-1564.

Note While the Maintainer acknowledges the existence of the issue, they believe it should be solved by sanitizing the inputStream to the parser

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade org.yaml:snakeyaml to version 1.26 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.5.8.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.5.8.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.5.8.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE

…and 10 more

Overview

org.springframework:spring-core is a core package within the spring-framework that contains multiple classes and utilities.

Affected versions of this package are vulnerable to Improper Input Validation when a user provides malicious input, causing insertion of additional log entries.

Remediation

Upgrade org.springframework:spring-core to version 5.2.19.RELEASE, 5.3.14 or higher.

References

Improper Input Validation vulnerability report

medium severity

Improper Output Neutralization for Logs

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.4.12.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.4.12.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@2.4.12.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE

…and 10 more

Overview

org.springframework:spring-core is a core package within the spring-framework that contains multiple classes and utilities.

Affected versions of this package are vulnerable to Improper Output Neutralization for Logs when a user provides malicious input, causing insertion of additional log entries.

Remediation

Upgrade org.springframework:spring-core to version 5.3.12, 5.2.18 or higher.

References

Improper Output Neutralization for Logs vulnerability report

medium severity

Stack-based Buffer Overflow

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Stack-based Buffer Overflow when parsing crafted untrusted YAML files, which can lead to a denial-of-service.

Remediation

Upgrade org.yaml:snakeyaml to version 1.31 or higher.

References

Stack-based Buffer Overflow vulnerability report

low severity

Stack-based Buffer Overflow

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Stack-based Buffer Overflow when parsing crafted untrusted YAML files, which can lead to a denial-of-service.

Remediation

Upgrade org.yaml:snakeyaml to version 1.32 or higher.

References

Stack-based Buffer Overflow vulnerability report

low severity

Stack-based Buffer Overflow

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Stack-based Buffer Overflow in org.yaml.snakeyaml.constructor.BaseConstructor.constructObject when parsing crafted untrusted YAML files, which can lead to a denial-of-service.

Remediation

Upgrade org.yaml:snakeyaml to version 1.31 or higher.

References

Stack-based Buffer Overflow vulnerability report

low severity

Stack-based Buffer Overflow

  • Vulnerable module: org.yaml:snakeyaml
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.yaml:snakeyaml@1.17
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.0.0.

Overview

org.yaml:snakeyaml is a YAML 1.1 parser and emitter for Java.

Affected versions of this package are vulnerable to Stack-based Buffer Overflow when supplied with untrusted input, due to improper limitation for incoming data.

Remediation

Upgrade org.yaml:snakeyaml to version 1.32 or higher.

References

Stack-based Buffer Overflow vulnerability report

low severity

Creation of Temporary File in Directory with Insecure Permissions

  • Vulnerable module: com.google.guava:guava
  • Introduced through: com.google.guava:guava@21.0

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.google.guava:guava@21.0
    Remediation: Upgrade to com.google.guava:guava@32.0.0-android.

Overview

com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.

Affected versions of this package are vulnerable to Creation of Temporary File in Directory with Insecure Permissions due to the use of Java's default temporary directory for file creation in FileBackedOutputStream. Other users and apps on the machine with access to the default Java temporary directory can access the files created by this class. This more fully addresses the underlying issue described in CVE-2020-8908, by deprecating the permissive temp file creation behavior.

NOTE: Even though the security vulnerability is fixed in version 32.0.0, the maintainers recommend using version 32.0.1, as version 32.0.0 breaks some functionality under Windows.

Remediation

Upgrade com.google.guava:guava to version 32.0.0-android, 32.0.0-jre or higher.

References

Creation of Temporary File in Directory with Insecure Permissions vulnerability report

low severity

Information Disclosure

  • Vulnerable module: com.google.guava:guava
  • Introduced through: com.google.guava:guava@21.0

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › com.google.guava:guava@21.0
    Remediation: Upgrade to com.google.guava:guava@30.0-android.

Overview

com.google.guava:guava is a set of core libraries that includes new collection types (such as multimap and multiset,immutable collections, a graph library, functional types, an in-memory cache and more.

Affected versions of this package are vulnerable to Information Disclosure. The file permissions on the file created by com.google.common.io.Files.createTempDir allow an attacker running a malicious program co-resident on the same machine to steal secrets stored in this directory. This is because, by default, on unix-like operating systems the /tmp directory is shared between all users, so if the correct file permissions aren't set by the directory/file creator, the file becomes readable by all other users on that system.

PoC

File guavaTempDir = com.google.common.io.Files.createTempDir();
System.out.println("Guava Temp Dir: " + guavaTempDir.getName());
runLS(guavaTempDir.getParentFile(), guavaTempDir); // Prints the file permissions -> drwxr-xr-x
File child = new File(guavaTempDir, "guava-child.txt");
child.createNewFile();
runLS(guavaTempDir, child); // Prints the file permissions -> -rw-r--r--

For Android developers, choosing a temporary directory API provided by Android is recommended, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.

Remediation

There is no fix for com.google.guava:guava. However, in version 30.0 and above, the vulnerable functionality has been deprecated. In oder to mitigate this vulnerability, upgrade to version 30.0 or higher and ensure your dependencies don't use the createTempDir or createTempFile methods.

References

Information Disclosure vulnerability report

low severity

Improper Handling of Case Sensitivity

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework.boot:spring-boot-starter@1.5.9.RELEASE

Detailed paths

  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.2.11.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.2.11.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-core@4.3.13.RELEASE
    Remediation: Upgrade to org.springframework.boot:spring-boot-starter@3.2.11.
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-expression@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE
  • Introduced through: garciapl/intercom@garciapl/intercom#222f02b5785b724f40b19d4d76859c17089e8431 › org.springframework.boot:spring-boot-starter@1.5.9.RELEASE › org.springframework.boot:spring-boot-autoconfigure@1.5.9.RELEASE › org.springframework.boot:spring-boot@1.5.9.RELEASE › org.springframework:spring-context@7.0.0-M3 › org.springframework:spring-aop@7.0.0-M3 › org.springframework:spring-beans@7.0.0-M3 › org.springframework:spring-core@4.3.13.RELEASE

…and 10 more

Overview

org.springframework:spring-core is a core package within the spring-framework that contains multiple classes and utilities.

Affected versions of this package are vulnerable to Improper Handling of Case Sensitivity due to String.toLowerCase() having some Locale dependent exceptions that could potentially result in fields not protected as expected.

Note:

The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive.

This vulnerability was also fixed in commercial versions 5.3.41 and 6.0.25.

Remediation

Upgrade org.springframework:spring-core to version 6.1.14 or higher.

References

Improper Handling of Case Sensitivity vulnerability report