Skip to content

Predictable passwords generated in AutoRegister

Moderate
hakusaro published GHSA-w3h6-j2gm-qf7q Jun 6, 2021

Package

AutoRegister (TShock for Terraria)

Affected versions

< 1.2.0.0

Patched versions

None

Description

Impact

The AutoRegister plugin generates passwords for the users that it registers in a predictable way, using their IPv4 address, their Client UUID, and their character name. Because of this, any server using AutoRegister may unexpectedly have its users impersonated. All of the ingredients used to create the passwords can be gathered by having a player connect to a malicious server. While much the same risk is involved if the player uses UUID based authentication, it is not made clear to server operators the risk here. For example, UUID login can be disabled. However, this plugin's damage has already been done at that point. It is trivial to attack a server retroactively, whereas UUID login can simply be disabled.

Patches

No patched version is available at this time.

Workarounds

For public servers, you should edit the database and change the bcrypt hashes to something that isn't predictable. Remove the plugin, and change the underlying passwords in the database.

For private servers, you may not need to do anything to "patch" the issue if you don't have users that play on other servers.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

CVE ID

No known CVE