{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41723 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41723 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41723 is a medium-severity vulnerability in Veeam One, published on 7 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41723 and fix it if it is affected.\n\nWhat it is: CVE-2023-41723 is a medium-severity vulnerability in Veeam One, published on 7 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-41723 in the wild and no public exploit code.\n\nAffected product: Veeam One. 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-41723/ (Markdown: https://insights.sbomify.com/CVE-2023-41723/index.md)","id":"CVE-2023-41723","markdown":"https://insights.sbomify.com/CVE-2023-41723/index.md","name":"CVE-2023-41723","record":{"aliases":["GHSA-2jf9-9rxc-j63c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Veeam ONE monitoring","requires_auth":"low_privilege","summary":"A read-only user can view dashboard schedules in Veeam ONE, exposing configuration details to unauthorized personnel.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"one","vendor":"veeam"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"A vulnerability in Veeam ONE allows a user with the Veeam ONE Read-Only User role to view the Dashboard Schedule. Note: The criticality of this vulnerability is reduced because the user with the Read-Only role is only able to view the schedule and cannot make changes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in One","id":"CVE-2023-41723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Sentry","id":"CVE-2023-41724"},"packages":[],"prev":{"headline":"Missing authorization in UniFi Network Application","id":"CVE-2023-41721"},"products":["One"],"published":"2023-11-07","related":[{"cvss_score":9.9,"headline":"Information disclosure in One","id":"CVE-2023-38547","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":9.8,"headline":"Information disclosure in One","id":"CVE-2023-38548","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":9.8,"headline":"Deserialization in One Agent","id":"CVE-2020-10914","kev_date_added":null,"published":"2020-04-22"},{"cvss_score":9.8,"headline":"Deserialization in One Agent","id":"CVE-2020-10915","kev_date_added":null,"published":"2020-04-22"},{"cvss_score":9.1,"headline":"Privilege escalation in One","id":"CVE-2024-42024","kev_date_added":null,"published":"2024-09-07"},{"cvss_score":9,"headline":"Information disclosure in One","id":"CVE-2024-42019","kev_date_added":null,"published":"2024-09-07"},{"cvss_score":7.8,"headline":"Privilege escalation in One","id":"CVE-2024-42023","kev_date_added":null,"published":"2024-09-07"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-29","vendors":["Veeam"]},"summary":"A read-only user can view dashboard schedules in Veeam ONE, exposing configuration details to unauthorized personnel.","url":"https://insights.sbomify.com/CVE-2023-41723/"}