lirantal/daloradius

GitHub

github.com

www.daloradius.com

Releases7

Frequency1 year 1 month

Last Release 23 days ago

Stars879

daloRADIUS is an advanced RADIUS web management application for managing hotspots and general-purpose ISP deployments. It features user management, graphical reporting, accounting, a billing engine, and integrates with OpenStreetMap for geolocation. The system is based on FreeRADIUS with which it shares access to the backend database.

CVE History

CVE	Published	CVSS v3	CVSS v2
CVE-2023-0338 ↗	Jan 17, 2023Tuesday, 17 January 2023, 16:15	6.1 MEDIUM	—
Cross-site Scripting (XSS) - Reflected in GitHub repository lirantal/daloradius prior to master-branch.
CVE-2023-0337 ↗	Jan 17, 2023Tuesday, 17 January 2023, 16:15	6.1 MEDIUM	—
Cross-site Scripting (XSS) - Reflected in GitHub repository lirantal/daloradius prior to master-branch.
CVE-2023-0048 ↗	Jan 4, 2023Wednesday, 4 January 2023, 14:15	8.8 HIGH	—
Code Injection in GitHub repository lirantal/daloradius prior to master-branch.
CVE-2023-0046 ↗	Jan 4, 2023Wednesday, 4 January 2023, 12:15	7.2 HIGH	—
Improper Restriction of Names for Files and Other Resources in GitHub repository lirantal/daloradius prior to master-branch.
CVE-2022-4630 ↗	Dec 21, 2022Wednesday, 21 December 2022, 18:15	5.3 MEDIUM	—
Sensitive Cookie Without 'HttpOnly' Flag in GitHub repository lirantal/daloradius prior to master.
CVE-2022-4366 ↗	Dec 8, 2022Thursday, 8 December 2022, 19:15	7.5 HIGH	—
Missing Authorization in GitHub repository lirantal/daloradius prior to master branch.
CVE-2022-23475 ↗	Dec 6, 2022Tuesday, 6 December 2022, 20:15	8.8 HIGH	—
daloRADIUS is an open source RADIUS web management application. daloRadius 1.3 and prior are vulnerable to a combination cross site scripting (XSS) and cross site request forgery (CSRF) vulnerability which leads to account takeover in the mng-del.php file because of an unescaped variable reflected in the DOM on line 116. This issue has been addressed in commit `ec3b4a419e`. Users are advised to manually apply the commit in order to mitigate this issue. Users may also mitigate this issue with in two parts 1) The CSRF vulnerability can be mitigated by making the daloRadius session cookie to samesite=Lax or by the implimentation of a CSRF token in all forms. 2) The XSS vulnerability may be mitigated by escaping it or by introducing a Content-Security policy.