Use of RSA Algorithm without OAEP

Property
Languagecsharp
Severityhigh
CWECWE-780: Use of RSA Algorithm without OAEP
OWASPA02:2021 - Cryptographic Failures
Confidence LevelMedium
Impact LevelMedium
Likelihood LevelHigh

Description

The code uses the outdated PKCS#1 v1.5 padding for RSA encryption, which is no longer considered secure. Modern best practices recommend using OAEP padding to protect sensitive data during encryption and key exchange.

Impact

If PKCS#1 v1.5 padding is used, attackers may be able to exploit known weaknesses to decrypt or tamper with encrypted data, potentially exposing confidential information or enabling unauthorized access to secure communications.

Use of RSA Algorithm without OAEP

Property
Languagescala
Severityhigh
CWECWE-780: Use of RSA Algorithm without OAEP
OWASPA02:2021 - Cryptographic Failures
Confidence LevelHigh
Impact LevelMedium
Likelihood LevelMedium

Description

The code uses RSA encryption without OAEP (Optimal Asymmetric Encryption Padding), which makes the encryption weaker and more vulnerable to attacks. Using RSA without proper padding can expose sensitive data.

Impact

If exploited, attackers could decrypt or tamper with encrypted data by exploiting weaknesses in the padding scheme. This can lead to exposure of confidential information, such as passwords or personal data, undermining the security of your application.

Use of Unmaintained Third Party Components

Property
Languagehcl
Severitylow
CWECWE-1104: Use of Unmaintained Third Party Components
OWASPA06:2021 - Vulnerable and Outdated Components
Confidence LevelLow
Impact LevelLow
Likelihood LevelLow

Description

The AWS ECR repository is not set to automatically scan container images for vulnerabilities when they are pushed. This means potentially unsafe images could be stored and deployed without any security checks.

Impact

Without image scanning on push, vulnerable or outdated components within container images may go undetected, increasing the risk of running insecure workloads. Attackers could exploit these vulnerabilities to gain unauthorized access, compromise applications, or affect the integrity of your infrastructure.

Use of Unmaintained Third Party Components

Property
Languagejavascript
Severitymedium
CWECWE-1104: Use of Unmaintained Third Party Components
OWASPA06:2021 - Vulnerable and Outdated Components
Confidence LevelLow
Impact LevelHigh
Likelihood LevelLow

Description

The code uses the notevil package, which is no longer maintained and contains known security vulnerabilities. Relying on outdated packages, especially those evaluating code, can introduce serious security risks.

Impact

Attackers could exploit vulnerabilities in notevil to execute malicious code, leading to data theft, unauthorized access, or complete compromise of the application and its users. Using unmaintained components increases the risk of undetected security flaws being exploited in production.

Use of Weak Hash

Property
Languageclojure
Severityhigh
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelHigh
Impact LevelHigh
Likelihood LevelMedium

Description

The code is using the MD5 hashing algorithm, which is outdated and insecure. MD5 can be easily broken, making it unsuitable for protecting sensitive data like passwords.

Impact

If this vulnerability is exploited, attackers can quickly crack hashed data such as passwords or tokens, leading to unauthorized access, data breaches, and potential compromise of user accounts or sensitive information.

Use of Weak Hash

Property
Languagego
Severitymedium
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelMedium
Impact LevelMedium
Likelihood LevelMedium

Description

Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead.

Use of Weak Hash

Property
Languagego
Severitymedium
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelMedium
Impact LevelMedium
Likelihood LevelMedium

Description

Detected SHA1 hash algorithm which is considered insecure. SHA1 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead.

Use of Weak Hash

Property
Languagekotlin
Severitymedium
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelMedium
Impact LevelMedium
Likelihood LevelLow

Description

The code uses the MD5 hash algorithm, which is outdated and vulnerable to collision attacks. MD5 should not be used for hashing sensitive data or as part of cryptographic operations.

Impact

Attackers can exploit MD5’s weaknesses to create different inputs that produce the same hash, potentially allowing them to bypass authentication, tamper with data, or forge digital signatures. This undermines data integrity and can expose sensitive information or compromise system security.

Use of Weak Hash

Property
Languagejava
Severityhigh
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelHigh
Impact LevelMedium
Likelihood LevelMedium

Description

The code uses the SHA-1 hashing algorithm, which is outdated and no longer considered secure because it is vulnerable to collisions. Applications should use stronger algorithms like SHA-256, SHA-512, or a dedicated password hashing function such as PBKDF2.

Impact

If SHA-1 is used for hashing sensitive data or digital signatures, attackers could exploit its weaknesses to generate collisions, potentially allowing unauthorized access, data tampering, or impersonation. This can lead to data breaches, loss of data integrity, and undermine trust in the application’s security.

Use of Weak Hash

Property
Languagejava
Severityhigh
CWECWE-328: Use of Weak Hash
OWASPA03:2017 - Sensitive Data Exposure
Confidence LevelHigh
Impact LevelMedium
Likelihood LevelMedium

Description

The code uses the MD5 hashing algorithm, which is outdated and insecure for cryptographic purposes. MD5 is vulnerable to collisions, making it unsuitable for securely hashing sensitive data or generating digital signatures.

Impact

Attackers could exploit MD5’s weaknesses to generate the same hash for different inputs, allowing them to tamper with data or bypass integrity checks. This can lead to data breaches, unauthorized access, or the compromise of authentication mechanisms in your application.