Skip to content

Wallabag user can reset data unintentionally

Moderate severity GitHub Reviewed Published Aug 21, 2023 in wallabag/wallabag • Updated Aug 24, 2023

Package

composer wallabag/wallabag (Composer)

Affected versions

>= 2.0.0-alpha.1, <= 2.6.2

Patched versions

2.6.3

Description

Description

wallabag was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily reset annotations, entries and tags, by the GET request to /reset/annotations, /reset/entries, /reset/tags, /reset/archived.

This vulnerability has a CVSSv3.1 score of 4.3.

You should immediately patch your instance to version 2.6.3 or higher if you have more than one user and/or having open registration.

Resolution

These actions are now doable only via POST method, which ensures that we can't do them via a 3rd-party website.

Credits

We would like to thank @zpbrent for reporting this issue through huntr.dev.

Reference: https://huntr.dev/bounties/4ee0ef74-e4d4-46e7-a05c-076bce522299/

References

@nicosomb nicosomb published to wallabag/wallabag Aug 21, 2023
Published to the GitHub Advisory Database Aug 21, 2023
Reviewed Aug 21, 2023
Last updated Aug 24, 2023

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
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:L/UI:R/S:U/C:N/I:H/A:N

EPSS score

0.051%
(22nd percentile)

Weaknesses

CVE ID

CVE-2023-4454

GHSA ID

GHSA-p8gp-899c-jvq9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.