Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 weeks ago
All versions
1.2.3+mc1.21.11
Release
AuthSecured 1.2.33 weeks ago 0
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Required content
Any compatible version
Changes
AuthSecured 1.2.3 Security Update
Recommended for every server. This release closes pre-login bypasses found in a security audit.
Added
- Fabric support for Minecraft 26.3, using Fabric API 0.164.0+26.3.
Security fixes
/changepasswordcan no longer be used to guess passwords before logging in. It now goes through the same rate limits, failed-attempt counter, account lock and temporary-password expiry checks as/login. Before login it only works to finish a temporary-password reset.- Fabric: players who have not logged in can no longer run commands through the signed-command
packet (
/msg,/me, or any command sent by a modified client). Every command is checked a second time right before it runs. - A locked account now gives the same answer for right and wrong passwords, so the lock cannot be used to confirm a guessed password.
- The built-in (non-Redis) rate limiter can no longer be flooded into locking every player out.
- Paper: if the plugin fails to start for any reason, new logins stay blocked instead of the server running without authentication.
Changes
- Players who have not logged in or registered cannot move at all: no walking, jumping,
riding, gliding, ender pearls, portals or spectator teleports. Looking around still works.
Controlled by
restrictions.freeze-player(enabled by default).
Fixes
- PostgreSQL: security audit events are stored correctly again. They were rejected before, which
also disabled the
max-accounts-per-ipregistration limit. - Spigot: all pre-login restrictions now load, and
/authadmin resetpasswordno longer needs Paper-only APIs.
Notes
- No configuration changes are required. Paper and Fabric remain separate downloads; each Fabric file targets one exact Minecraft version and requires Fabric API.
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:z4naQApQ:lCBRZ0Fd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z4naQApQ:lCBRZ0Fd"
}

