Vulnerabilities

7 via 7 paths

Dependencies

9

Source

GitHub

Commit

b8a79f0c

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 6
Status
  • 7
  • 0
  • 0

high severity
new

Infinite loop

  • Vulnerable module: org.bouncycastle:bcprov-jdk18on
  • Introduced through: com.hierynomus:smbj@0.12.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e com.hierynomus:smbj@0.12.1 org.bouncycastle:bcprov-jdk18on@1.75

Overview

Affected versions of this package are vulnerable to Infinite loop in ED25519 verification in the ScalarUtil class. An attacker can send a malicious signature and public key to trigger denial of service.

Remediation

Upgrade org.bouncycastle:bcprov-jdk18on to version 1.78 or higher.

References

medium severity

Rebind Flaw

  • Vulnerable module: org.apache.camel:camel-core
  • Introduced through: org.apache.camel:camel-core@2.22.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e org.apache.camel:camel-core@2.22.1
    Remediation: Upgrade to org.apache.camel:camel-core@3.2.0.

Overview

org.apache.camel:camel-core is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful bean integration.

Affected versions of this package are vulnerable to Rebind Flaw in Apache Camel's JMX.

Remediation

Upgrade org.apache.camel:camel-core to version 3.2.0 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: org.apache.camel:camel-core
  • Introduced through: org.apache.camel:camel-core@2.22.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e org.apache.camel:camel-core@2.22.1
    Remediation: Upgrade to org.apache.camel:camel-core@2.22.3.

Overview

org.apache.camel:camel-core is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful bean integration.

Affected versions of this package are vulnerable to Directory Traversal. The file producer allows writing files to directories outside its starting directory.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade org.apache.camel:camel-core to version 2.21.5, 2.22.3, 2.23.1 or higher.

References

medium severity
new

Observable Discrepancy

  • Vulnerable module: org.bouncycastle:bcprov-jdk18on
  • Introduced through: com.hierynomus:smbj@0.12.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e com.hierynomus:smbj@0.12.1 org.bouncycastle:bcprov-jdk18on@1.75

Overview

Affected versions of this package are vulnerable to Observable Discrepancy due to the timing difference between exceptions thrown when processing RSA key exchange handshakes, AKA Marvin.

Note: The implemented fix mitigates the leakage of data via the PKCS#1 interface, but does not fully alleviate the side-channel as it allows cases in which the padding check fails but the handshake succeeds.

Remediation

Upgrade org.bouncycastle:bcprov-jdk18on to version 1.78 or higher.

References

medium severity

Observable Timing Discrepancy

  • Vulnerable module: org.bouncycastle:bcprov-jdk18on
  • Introduced through: com.hierynomus:smbj@0.12.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e com.hierynomus:smbj@0.12.1 org.bouncycastle:bcprov-jdk18on@1.75

Overview

Affected versions of this package are vulnerable to Observable Timing Discrepancy via the PKCS#1 1.5 and OAEP decryption process. An attacker can recover ciphertexts via a side-channel attack by exploiting the Marvin security flaw. The PKCS#1 1.5 attack vector leaks data via javax.crypto.Cipher exceptions and the OAEP interface vector leaks via the bit size of the decrypted data.

Remediation

Upgrade org.bouncycastle:bcprov-jdk18on to version 1.78 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: commons-io:commons-io
  • Introduced through: commons-io:commons-io@2.5

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e commons-io:commons-io@2.5
    Remediation: Upgrade to commons-io:commons-io@2.7.

Overview

commons-io:commons-io is a The Apache Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more.

Affected versions of this package are vulnerable to Directory Traversal via calling the method FileNameUtils.normalize using an improper string like //../foo or \\..\foo, which may allow access to files in the parent directory.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade commons-io:commons-io to version 2.7 or higher.

References

medium severity
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: org.bouncycastle:bcprov-jdk18on
  • Introduced through: com.hierynomus:smbj@0.12.1

Detailed paths

  • Introduced through: jborza/camel-smbj@jborza/camel-smbj#b8a79f0c33aebce874e29614cb29d5c98abbaa4e com.hierynomus:smbj@0.12.1 org.bouncycastle:bcprov-jdk18on@1.75

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the solveQuadraticEquation() function used for certificate verification in ECCurve.java. Passing a large f2m parameter can cause excessive CPU consumption.

Remediation

Upgrade org.bouncycastle:bcprov-jdk18on to version 1.78 or higher.

References