Tags
Creators
Details
1.6
Compatibility
Changes
Critical & High Severity
Request/Response Mix-up – prevented user data from being sent to wrong users.
Potential Remote Code Execution (RCE) – fixed vulnerability with partial PUT requests.
DoS in multipart upload – mitigated Denial of Service attacks.
TOCTOU Race Conditions – fixed Time-of-Check to Time-of-Use timing issues.
Resource Shutdown Issues – corrected improper resource management.
Regular Expression Denial of Service (ReDoS) – in TimeUtils.java, unsafe regex patterns fixed.
Moderate & Low Severity
Security constraint bypasses – ensured constraints cannot be bypassed.
HTTP priority header DoS – mitigated potential Denial of Service via HTTP headers.
CGI and rewrite rule bypasses – fixed vulnerabilities allowing rule circumvention.
Unbounded Input Handling – limited maximum input length in time parsing.
Unsafe Time Parsing – ensured integers are only parsed after regex validation.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:QsS6k1xF:hU99c9Vd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QsS6k1xF:hU99c9Vd"
}

