{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0046 exists.","fix":"No fix has been published for CVE-2023-0046 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0046 is a high-severity path traversal vulnerability in lirantal/daloradius, published on 4 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-0046 and fix it if it is affected.\n\nWhat it is: CVE-2023-0046 is a high-severity path traversal vulnerability in lirantal/daloradius, published on 4 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0046 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-2023-0046/ (Markdown: https://insights.sbomify.com/CVE-2023-0046/index.md)","id":"CVE-2023-0046","markdown":"https://insights.sbomify.com/CVE-2023-0046/index.md","name":"CVE-2023-0046","record":{"aliases":["GHSA-9rw8-hqcq-vxh4"],"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":"high_privilege","summary":"Attackers can exploit improper file name restrictions in DaloRADIUS to access or modify unauthorized files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"daloradius","vendor":"daloradius"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-641","name":"Improper Restriction of Names for Files and Other Resources"}],"description":"Improper Restriction of Names for Files and Other Resources 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":"Improper Restriction of Names for Files and Other Resources in lirantal/daloradius","id":"CVE-2023-0046","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2023-0047"},"packages":[],"prev":{"headline":"Incorrect indirect branch prediction barrier in the Linux Kernel","id":"CVE-2023-0045"},"products":["lirantal/daloradius"],"published":"2023-01-04","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":"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"},{"cvss_score":5.3,"headline":"Missing Authorization in lirantal/daloradius","id":"CVE-2022-4366","kev_date_added":null,"published":"2022-12-08"}],"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-09","vendors":["lirantal"]},"summary":"Attackers can exploit improper file name restrictions in DaloRADIUS to access or modify unauthorized files.","url":"https://insights.sbomify.com/CVE-2023-0046/"}