Wallabag user can disable 2FA unintentionally

published 2023-10-02 3y ago modified 2024-12-07 last yr.

cvss: 4.3; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

## Impact wallabag was discovered to contain a Cross-Site Request Forgery (CSRF) which allows attackers to arbitrarily disable 2FA through `/config/otp/app/disable` and `/config/otp/email/disable`.

This vulnerability has a CVSSv3.1 score of 4.3.

**You should upgrade your instance to version 2.6.7 or higher.**

## Resolution

These endpoints now require POST method.

## Credits

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

Reference: https://huntr.dev/bounties/4c446fe7-2a44-4907-b0cf-4ab77d75c487/

Patch / fix

fixed in 1 links 1

packagist wallabag/wallabag 2.6.7

github.com/wallabag/wallabag@0cfdddc commit

Is GHSA-56fm-hfp3-x3w3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	wallabag/wallabag	>=2.0.0-alpha.1, <2.6.7	2.6.7

References

Sources

GitHub Advisory GHSA-56fm-hfp3-x3w3

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.