CVE-2023-0610: wallabag subject to Improper Authorization via annotations
Impact The annotations feature lets users add annotations on highlighted parts of an entry.
The controller does not validate authorization on PUT and DELETE requests which lets a logged user modify or delete any annotation using their ID on their endpoints example.org/annotations/{id}.
These vulnerable requests also disclose highlighted parts of the entry to the attacker.
You should immediately patch your instance to version 2.5.3 or higher if you have more than one user and/or having open registration.
Resolution
A user check is now done in the vulnerable methods before applying change on an annotation.
The Annotation retrieval through a ParamConverter has also been replaced with a call to the AnnotationRepository in order to prevent any information disclosure through response discrepancy.
Workarounds
Credits
We would like to thank @bAuh0lz for reporting this issue through huntr.dev.
Reference: https://huntr.dev/bounties/8fdd9b31-d89b-4bbe-9557-20b960faf926/
Other sources
Improper Authorization in GitHub repository wallabag/wallabag prior to 2.5.3.
wallabag subject to Improper Authorization via annotations
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/wallabag/wallabagto a version that resolves this vulnerability.Fixed in 2.5.3 - Upgrade
Upgrade
wallabag/wallabagto a version that resolves this vulnerability.Fixed in 2.5.3
Event History
Frequently Asked Questions
What is the severity of CVE-2023-0610?
The severity of CVE-2023-0610 is classified as a high-risk vulnerability due to improper authorization in Wallabag software.
How do I fix CVE-2023-0610?
To fix CVE-2023-0610, update Wallabag to version 2.5.3 or later.
What types of systems are affected by CVE-2023-0610?
CVE-2023-0610 affects all versions of Wallabag prior to 2.5.3.
What is the impact of CVE-2023-0610?
The impact of CVE-2023-0610 includes potential unauthorized access to sensitive user data.
Is there a workaround for CVE-2023-0610?
There is no known workaround for CVE-2023-0610; updating to the latest version is recommended.