Total
7 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2023-0338 | 1 Daloradius | 1 Daloradius | 2023-01-23 | N/A | 6.1 MEDIUM |
| Cross-site Scripting (XSS) - Reflected in GitHub repository lirantal/daloradius prior to master-branch. | |||||
| CVE-2023-0337 | 1 Daloradius | 1 Daloradius | 2023-01-23 | N/A | 6.1 MEDIUM |
| Cross-site Scripting (XSS) - Reflected in GitHub repository lirantal/daloradius prior to master-branch. | |||||
| CVE-2023-0046 | 1 Daloradius | 1 Daloradius | 2023-01-10 | N/A | 7.2 HIGH |
| Improper Restriction of Names for Files and Other Resources in GitHub repository lirantal/daloradius prior to master-branch. | |||||
| CVE-2023-0048 | 1 Daloradius | 1 Daloradius | 2023-01-10 | N/A | 8.8 HIGH |
| Code Injection in GitHub repository lirantal/daloradius prior to master-branch. | |||||
| CVE-2022-4630 | 1 Daloradius | 1 Daloradius | 2022-12-28 | N/A | 5.3 MEDIUM |
| Sensitive Cookie Without 'HttpOnly' Flag in GitHub repository lirantal/daloradius prior to master. | |||||
| CVE-2022-4366 | 1 Daloradius | 1 Daloradius | 2022-12-12 | N/A | 7.5 HIGH |
| Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitHub repository lirantal/daloradius prior to master branch. | |||||
| CVE-2022-23475 | 1 Daloradius | 1 Daloradius | 2022-12-12 | N/A | 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. | |||||