{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4366 exists.","fix":"No fix has been published for CVE-2022-4366 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4366 is a medium-severity missing authorization vulnerability in lirantal/daloradius, published on 8 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4366 and fix it if it is affected.\n\nWhat it is: CVE-2022-4366 is a medium-severity missing authorization vulnerability in lirantal/daloradius, published on 8 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4366 exists.\n\nAffected product: lirantal/daloradius. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-4366/ (Markdown: https://insights.sbomify.com/CVE-2022-4366/index.md)","id":"CVE-2022-4366","markdown":"https://insights.sbomify.com/CVE-2022-4366/index.md","name":"CVE-2022-4366","record":{"aliases":["GHSA-4gv4-7phc-2jw7"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RADIUS management web app","requires_auth":"none","summary":"Attackers can access or modify data without proper authorization in the DaloRADIUS web application.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"daloradius","vendor":"daloradius"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization in GitHub repository lirantal/daloradius prior to master branch.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Missing Authorization in lirantal/daloradius","id":"CVE-2022-4366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Duplicate, use CVE-2023-4279 instead.","id":"CVE-2022-4367"},"packages":[],"prev":{"headline":"Information disclosure in GitLab","id":"CVE-2022-4365"},"products":["lirantal/daloradius"],"published":"2022-12-08","related":[{"cvss_score":8.8,"headline":"dalorRadius full account take over","id":"CVE-2022-23475","kev_date_added":null,"published":"2022-12-06"},{"cvss_score":7.2,"headline":"Improper Restriction of Names for Files and Other Resources in lirantal/daloradius","id":"CVE-2023-0046","kev_date_added":null,"published":"2023-01-04"},{"cvss_score":7.2,"headline":"Code Injection in lirantal/daloradius","id":"CVE-2023-0048","kev_date_added":null,"published":"2023-01-04"},{"cvss_score":5.8,"headline":"Cross-site Scripting (XSS) - Reflected in lirantal/daloradius","id":"CVE-2023-0337","kev_date_added":null,"published":"2023-01-17"},{"cvss_score":5.8,"headline":"Cross-site Scripting (XSS) - Reflected in lirantal/daloradius","id":"CVE-2023-0338","kev_date_added":null,"published":"2023-01-17"},{"cvss_score":5.3,"headline":"Sensitive Cookie Without 'HttpOnly' Flag in lirantal/daloradius","id":"CVE-2022-4630","kev_date_added":null,"published":"2022-12-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-14","vendors":["lirantal"]},"summary":"Attackers can access or modify data without proper authorization in the DaloRADIUS web application.","url":"https://insights.sbomify.com/CVE-2022-4366/"}