Vulnerabilities · 2021 · Akaunting
CVE-2021-36804
Akaunting vulnerability
Akaunting version 2.1.12 and earlier suffers from a password reset spoofing vulnerability, wherein an attacker can proxy password reset requests through a running Akaunting instance, if that attacker knows the target's e-mail address. This issue was fixed in version 2.1.13 of the product. Please note that this issue is ultimately caused by the defaults provided by the Laravel framework, specifically how proxy headers are handled with respect to multi-tenant implementations. In other words, while this is not technically a vulnerability in Laravel, this default configuration is very likely to lead to practically identical identical vulnerabilities in Laravel projects that implement multi-tenant applications.
Affected products
Akaunting. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Akaunting runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/laravel/laravel/pull/5477 · Patch
- www.laravel-enlightn.com/docs/security/host-injection-analyzer.html · Third Party Advisory
- www.rapid7.com/blog/post/2021/07/27/multiple-open-source-web-app-vulnerabilities-fixed/ · Exploit
- nvd.nist.gov/vuln/detail/CVE-2021-36804
- cve.org/CVERecord?id=CVE-2021-36804
More vulnerabilities in Akaunting products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.