{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4630 exists.","fix":"No fix has been published for CVE-2022-4630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4630 is a medium-severity vulnerability in lirantal/daloradius, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-4630 and fix it if it is affected.\n\nWhat it is: CVE-2022-4630 is a medium-severity vulnerability in lirantal/daloradius, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4630 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-4630/ (Markdown: https://insights.sbomify.com/CVE-2022-4630/index.md)","id":"CVE-2022-4630","markdown":"https://insights.sbomify.com/CVE-2022-4630/index.md","name":"CVE-2022-4630","record":{"aliases":["GHSA-xj56-q6pv-vrx6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RADIUS management web app","requires_auth":"none","summary":"Attackers can steal sensitive session cookies via XSS because the HttpOnly flag is missing, allowing session hijacking in DaloRADIUS.","user_interaction":"required","vuln_class":"information_disclosure"},"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:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-1004","name":"Sensitive Cookie Without 'HttpOnly' Flag"}],"description":"Sensitive Cookie Without 'HttpOnly' Flag in GitHub repository lirantal/daloradius prior to master.","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":"Sensitive Cookie Without 'HttpOnly' Flag in lirantal/daloradius","id":"CVE-2022-4630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"WP-Ban ban-options.php cross site scripting","id":"CVE-2022-4631"},"packages":[],"prev":{"headline":"Product Slider for WooCommerce \u003c 2.6.4 - Contributor+ Stored XSS in Shortcode","id":"CVE-2022-4629"},"products":["lirantal/daloradius"],"published":"2022-12-21","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":"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-14","vendors":["lirantal"]},"summary":"Attackers can steal sensitive session cookies via XSS because the HttpOnly flag is missing, allowing session hijacking in DaloRADIUS.","url":"https://insights.sbomify.com/CVE-2022-4630/"}