Skip to content

Appeal secret key should not expose data from just having URL

High
dqwiki published GHSA-p247-r7fj-jmm5 Feb 12, 2023

Package

routes (UTRS)

Affected versions

>=2.0

Patched versions

Pending version tag

Description

Impact

Who is impacted?
This vulnerability allows for the public exposure of appeals to the general public, provided that one has the full url of the appeal including the query string, as the query string contains the full appeal key. If the ticket is open, this would allow an individual to falsely post as if they were the appellant. This potentially affects every user, and it allows for permanent, public internet archiving of appeals by anyone with access to the full url, thereby exposing appellants to unknown risks.

The query string for the URL could be saved in the browser's history, passed through referrers to other web sites, stored in web logs, or otherwise recorded in other sources. As the query string contains sensitive information (the appeal keys), attackers can use this information to launch impersonation attacks indefinitely.

Patches

Has the problem been patched? What versions should users upgrade to?
There is no patch as of 11 February 2023.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
The only remediation is to never share the full url of one's appeal to anyone, as the full url contains the appeal key.

References

Are there any links users can visit to find out more?
No. Please do not attempt to find these on internet archive websites.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
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:H/I:H/A:N

CVE ID

No known CVE

Weaknesses

Credits