Skip to content

SQL Injection vulnerability in webserver endpoint

High
AuroraLS3 published GHSA-mcq3-5hhm-75rx Jan 15, 2023

Package

maven com.djrapitops.Plan (Maven)

Affected versions

5.2 build 1168 < 5.5 build 2163

Patched versions

5.5 build 2172

Description

Impact

Vulnerable versions: 5.2 build 1168 to 5.5 build 2163

SQL Injection allows a malicious actor to read any data from the database and change or delete data. This may expose user salted+hashed Plan web user passwords or other data in the database.

if login is enabled: Malicious users with access to /players-page can access an endpoint which was found to contain an SQL Injection vulnerability.
if login is not enabled: Any malicious actor can access an endpoint which was found to contain an SQL Injection vulnerability.

Patches

Fixed in 5.5 build 2172 https://github.com/plan-player-analytics/Plan/releases/tag/5.5.2172

A backport fix for version 5.4 build 1722 can be found here for those still running Java 8 or Sponge 7 https://github.com/plan-player-analytics/Plan/releases/tag/5.4.1722.1

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Mitigation options if you are unable to update

  1. Enable https and login so that less users have access to the vulnerable endpoint.
    https://github.com/plan-player-analytics/Plan/wiki/SSL-Certificate-(HTTPS)-Set-Up
  2. Enable IP Whitelist so that less users have access to the vulnerable endpoint.
Webserver:
  Security:
    IP_whitelist:
      Enabled: true
  1. if unable to update or secure the server, disable Plan Webserver. This option is good if you want to delay updating to a more convenient time.
Webserver:
  Disable_webserver: true

Severity

High

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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:N/S:U/C:H/I:L/A:L

CVE ID

No known CVE

Weaknesses