0.1.1-beta

Vulnerability Report

delvelin-plugin

Path: /Volumes/DATA/Projects/Kotlin/delvelin-plugin


CWE-400 - Apache Log4j 1.x (EOL) allows Denial of Service (DoS) 1 issues
org.apache.logging.log4j:log4j-core:2.0-beta9
** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. https://nvd.nist.gov/vuln/detail/CVE-2023-26464
CWE-379 - Guava vulnerable to insecure use of temporary directory 1 issues
com.google.guava:guava:31.1-jre
Use of Java's default temporary directory for file creation in `FileBackedOutputStream` in Google Guava versions 1.0 to 31.1 on Unix systems and Android Ice Cream Sandwich allows other users and apps on the machine with access to the default Java temporary directory to be able to access the files created by the class. Even though the security vulnerability is fixed in version 32.0.0, maintainers recommend using version 32.0.1 as version 32.0.0 breaks some functionality under Windows. https://nvd.nist.gov/vuln/detail/CVE-2023-2976
CWE-798 - Hardcoded Secrets and Credentials 62 issues
username = project.findProperty("repoUsername") as
Warning: Hardcoded secrets or credentials found in the source code. Hardcoding sensitive information such as passwords, tokens, and API keys can expose secrets and increase the risk of data leaks.
password = project.findProperty("repoPassword") as
val keyStore = KeyStore.getInstance(KeyStore.getDe
keyStore.load(null, null)
trustManagerFactory.init(keyStore)
private static final Path basePath = Paths.get(Sys
// Show save dialog and get the user's choice
int userSelection = fileChooser.showSaveDialog(nul
this.className = className;
String className;
return className;
itemFiles.add(new ItemFile(specificLocation, ext, 
String className;
this.className = className;
return className;
public static void addToReport(String cweCode, Str
newItem.setClassName(className);
.collect(Collectors.groupingBy(ItemReport::getCweC
String cweCode = entry.getKey();
// Grouping reports by CWE Code
.collect(Collectors.groupingBy(ItemReport::getCweC
String cweCode = entry.getKey();
String ext = entry.getKey();
String cweLabels = cweCounts.keySet()
String cweLabels = cweCounts.keySet()
// Grouping reports by CWE Code
.collect(Collectors.groupingBy(ItemReport::getCweC
.append(entry.getKey())
String cweCode = entry.getKey();
//            .collect(Collectors.groupingBy(ext -
.collect(Collectors.groupingBy(ext -> ext, Collect
String msg = "Warning: Hardcoded secrets or creden
"and API keys can expose secrets and increase the 
private static final Pattern KEYWORD_PATTERN = Pat
"(password|pwd|passwd|pass|user_password|user_pwd|
List sensitiveKeys = Arrays.asList("passwo
"auth_token", "token", "session_token", "oauth_tok
"secret_key", "api_token", "jwt_token", "jwt_secre
"ssh_key", "rsa_key", "dsa_key", "ecdsa_key", "x50
"secret_access_key", "security_key", "symmetric_ke
"authentication", "login", "userid", "user_id", "u
"license_key", "account_number", "bank_account", "
this.vulnerabilities = Vulnerabilities.HARDCODED_S
private final List ignoredKeys = Arrays.as
if (ignoredKeys.stream().noneMatch(line::contains)
Matcher matcher = KEYWORD_PATTERN.matcher(line);
new HardCodedSecretDetector(),
new WeakAlgorithm("(?i)Cipher\\s*\\.\\s*getInstanc
new WeakAlgorithm("(?i)Cipher\\s*\\.\\s*getInstanc
new WeakAlgorithm("(?i)KeyPairGenerator\\s*\\.\\s*
new WeakAlgorithm("(?i)KeyPairGenerator\\s*\\.\\s*
public String className;
className = pathStr;
className = pathStr.replace(SourceSet.SEP, ".")
Reports.detect("",extName, className);
return (Config.outputFileFormat == OutputFileForma
message, priority, className, extName);
message, vulnerabilities.getPriority(), className,
HARDCODED_SECRETS("Hardcoded Secrets and Credentia
INADEQUATE_AUTHENTICATION("Inadequate Authenticati
public static final String PINK = Config.outputFil
public static final String BRIGHT_PINK = Config.ou
CWE-502 - Incomplete fix for Apache Log4j vulnerability 1 issues
org.apache.logging.log4j:log4j-core:2.0-beta9
# Impact The fix to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack. ## Affected packages Only the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use. # Mitigation Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). Log4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property `log4j2.formatMsgNoLookups` to `true` do NOT mitigate this specific vulnerability. https://nvd.nist.gov/vuln/detail/CVE-2021-45046
CWE-20 - Improper Input Validation and Injection in Apache Log4j2 1 issues
org.apache.logging.log4j:log4j-core:2.0-beta9
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages Only the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use. This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited. https://nvd.nist.gov/vuln/detail/CVE-2021-44832
CWE-319 - HTTP Connection without SSL/TLS 5 issues
val urlString = "http://example.com" // Menggunaka
Insecure HTTP detected
val connection = url.openConnection() as HttpURLCo
if (line.contains("HttpURLConnection") ||
HttpURLConnection connection = (HttpURLConnection)
HttpURLConnection connection = null;
CWE-173 - Information Disclosure in Guava 1 issues
com.google.guava:guava:31.1-jre
A temp directory creation vulnerability exists in Guava prior to version 32.0.0 allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava `com.google.common.io.Files.createTempDir()`. The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. Maintainers recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method. https://nvd.nist.gov/vuln/detail/CVE-2020-8908
CWE-295 - Improper validation of certificate with host mismatch in Apache Log4j SMTP appender 1 issues
org.apache.logging.log4j:log4j-core:2.0-beta9
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender prior to version 2.13.2. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. https://nvd.nist.gov/vuln/detail/CVE-2020-9488
CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition) 12 issues
StringBuilder
Consider using StringBuffer
StringBuilder
StringBuilder
StringBuilder
StringBuilder
StringBuilder
Queue
Consider using ConcurrentLinkedQueue or LinkedBlockingQueue
HashMap
Consider using ConcurrentHashMap or Collections.synchronizedMap(new HashMap<>())
HashMap
StringBuilder
Consider using StringBuffer
StringBuilder
StringBuilder

CWE Issues Distribution