deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webmvc (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.1.0, <= 6.1.26
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webmvc (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.2.0, <= 6.2.17
Patched in: 6.2.18

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webmvc (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 7.0.0, <= 7.0.6
Patched in: 7.0.7

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webflux (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: <= 5.3.47
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webflux (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.1.0, <= 6.1.26
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webflux (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.2.0, <= 6.2.17
Patched in: 6.2.18

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-6p4f-wcwh-5vvm
Package: org.springframework:spring-webflux (MAVEN)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 7.0.0, <= 7.0.6
Patched in: 7.0.7

Summary: Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources

Details:
Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is serving static resources from the file system
  *  the application is running on a Windows platform


When all the conditions above are met, the attacker can send malicious requests that are slow to resolve and that can keep HTTP connections in use. This can cause a Denial of Service on the application.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webmvc (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: <= 5.3.47
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webmvc (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 6.1.0, <= 6.1.26
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webmvc (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 6.2.0, <= 6.2.17
Patched in: 6.2.18

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webmvc (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 7.0.0, <= 7.0.6
Patched in: 7.0.7

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: <= 5.3.47
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 6.1.0, <= 6.1.26
Patched in: unpatched

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 6.2.0, <= 6.2.17
Patched in: 6.2.18

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-wg35-8jpf-2xv3
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-524: Use of Cache Containing Sensitive Information
Vulnerable versions: >= 7.0.0, <= 7.0.6
Patched in: 7.0.7

Summary: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.

Details:
Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources.


More precisely, an application can be vulnerable when all the following are true:

  *  the application is using Spring MVC or Spring WebFlux
  *  the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled
  *  the application adds support for encoded resources resolution
  *  the resource cache must be empty when the attacker has access to the application


When all the conditions above are met, the attacker can send malicious requests and poison the resource cache with resources using the wrong encoding. This can cause a denial of service by breaking the front-end application for clients.
GitHub Security Advisory: GHSA-5843-p793-ghmm
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: <= 5.3.47
Patched in: unpatched

Summary: Spring Framework DoS with Multipart Temp Files in WebFlux

Details:
A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space.

Older, unsupported versions are also affected.
GitHub Security Advisory: GHSA-5843-p793-ghmm
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.1.0, <= 6.1.26
Patched in: unpatched

Summary: Spring Framework DoS with Multipart Temp Files in WebFlux

Details:
A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space.

Older, unsupported versions are also affected.
GitHub Security Advisory: GHSA-5843-p793-ghmm
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 6.2.0, <= 6.2.17
Patched in: 6.2.18

Summary: Spring Framework DoS with Multipart Temp Files in WebFlux

Details:
A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space.

Older, unsupported versions are also affected.
GitHub Security Advisory: GHSA-5843-p793-ghmm
Package: org.springframework:spring-webflux (MAVEN)
Severity: LOW (CVSS 0.0)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: >= 7.0.0, <= 7.0.6
Patched in: 7.0.7

Summary: Spring Framework DoS with Multipart Temp Files in WebFlux

Details:
A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K. Under some circumstances, temp files may remain not deleted after the request is fully processed. This allows an attacker to consume available disk space.

Older, unsupported versions are also affected.
GitHub Security Advisory: GHSA-gw2x-mfwr-h46p
Package: com.xuxueli:xxl-job-admin (MAVEN)
Severity: LOW (CVSS 3.7)
CWE: CWE-99: Improper Control of Resource Identifiers ('Resource Injection')
Vulnerable versions: < 3.4.0
Patched in: 3.4.0

Summary: xxl-job has a Resource Injection issue

Details:
A security flaw has been discovered in Xuxueli xxl-job up to 3.3.2. Impacted is the function logDetailCat of the file xxl-job-admin/src/main/java/com/xxl/job/admin/controller/biz/JobLogController.java of the component Execution Log Handler. The manipulation of the argument logId results in improper control of resource identifiers. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is considered difficult. The exploit has been released to the public and may be used for attacks. Upgrading to version 3.4.0 is recommended to address this issue. The patch is identified as d24e4ccd6073cc75305e1d3b9c29bc8db7437e7a. It is suggested to upgrade the affected component.
GitHub Security Advisory: GHSA-j7j9-5253-f7vh
Package: com.ritense.valtimo:contract (MAVEN)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: >= 13.4.0, < 13.23.0
Patched in: 13.23.0

Summary: Valtimo has SpEL injection via StandardEvaluationContext that allows Remote Code Execution by admin users

Details:
### Summary

Multiple classes evaluate Spring Expression Language (SpEL) expressions from user-supplied input using `StandardEvaluationContext`, which provides unrestricted access to Java types and methods. An authenticated user with the ADMIN role can achieve Remote Code Execution and credential exfiltration.

### Impact

An attacker with ADMIN credentials can:
- **Execute arbitrary OS commands** via `T(java.lang.Runtime).getRuntime().exec('...')`
- **Exfiltrate all environment variables** (database passwords, API keys, Keycloak secrets) via `T(java.lang.System).getenv()`
- **Read JVM system properties** via `T(java.lang.System).getProperties()`
- **Load arbitrary classes** via `T(java.lang.Class).forName('...')`

### Affected Components

**1. DocumentMigrationService** (since 12.0.0)

Exploitable through the document migration REST API:
- `POST /api/management/v1/document-definition/migrate`
- `POST /api/management/v1/document-definition/migration/conflicts`

The malicious SpEL expression is supplied in the `source` or `target` field of a `DocumentMigrationPatch` object in the request body, using the `${...}` template syntax.

- In 12.x: `com.ritense.document.service.DocumentMigrationService#handleSpelExpression` (document module)
- In 13.x: same class, moved to the case module

**2. Condition** (since 13.4.0)

Exploitable through any admin-configured widget, dashboard, or feature that uses the `Condition` framework. The SpEL expression is supplied in the `value` field of a condition's JSON configuration.

- `com.ritense.valtimo.contract.conditions.Condition#resolveValue` (contract module)

This component has a significantly wider attack surface than DocumentMigrationService, as conditions are used across many modules.

### Remediation

Replace `StandardEvaluationContext` with `SimpleEvaluationContext` in both affected classes, which disallows Java type references and arbitrary method invocation:

```kotlin
val evaluationContext = SimpleEvaluationContext
    .forPropertyAccessors(MapAccessor(), jsonPropertyAccessor)
    .build()
```