{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-44795 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-44795 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44795 is a medium-severity vulnerability in n/a, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-44795 and fix it if it is affected.\n\nWhat it is: CVE-2022-44795 is a medium-severity vulnerability in n/a, published on 7 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-44795 in the wild and no public exploit code.\n\nAffected product: n/a. 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-44795/ (Markdown: https://insights.sbomify.com/CVE-2022-44795/index.md)","id":"CVE-2022-44795","markdown":"https://insights.sbomify.com/CVE-2022-44795/index.md","name":"CVE-2022-44795","record":{"aliases":["GHSA-fxhg-25q8-4697"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Backup appliance software","requires_auth":"low_privilege","summary":"An attacker with credentials can predict support bundle URLs due to insecure RNG, leading to local information disclosure of system logs.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ootbi","vendor":"objectfirst"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"An issue was discovered in Object First Ootbi BETA build 1.0.7.712. A flaw was found in the Web Service, which could lead to local information disclosure. The command that creates the URL for the support bundle uses an insecure RNG. That can lead to prediction of the generated URL. As a result, an attacker can get access to system logs. An attacker would need credentials to exploit this vulnerability. This is fixed in Object First Ootbi BETA build 1.0.13.1611. Important note - This vulnerability is related to the Object First Ootbi BETA version, which is not released for production and therefore has no impact on the production environment. The production-ready Object First Ootbi version will have this vulnerability fixed.","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":"Weak cryptography in n/a","id":"CVE-2022-44795","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2022-44796"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2022-44794"},"products":["n/a"],"published":"2022-11-07","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2022-44796","kev_date_added":null,"published":"2022-11-07"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-44794","kev_date_added":null,"published":"2022-11-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":"2025-05-01","vendors":["n/a"]},"summary":"An attacker with credentials can predict support bundle URLs due to insecure RNG, leading to local information disclosure of system logs.","url":"https://insights.sbomify.com/CVE-2022-44795/"}