{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45177 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-45177 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45177 is a high-severity vulnerability in n/a, published on 21 Feb 2024. 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-45177 and fix it if it is affected.\n\nWhat it is: CVE-2022-45177 is a high-severity vulnerability in n/a, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-45177 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-45177/ (Markdown: https://insights.sbomify.com/CVE-2022-45177/index.md)","id":"CVE-2022-45177","markdown":"https://insights.sbomify.com/CVE-2022-45177/index.md","name":"CVE-2022-45177","record":{"aliases":["GHSA-g759-2x5w-f89c"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LIVEBOX Collaboration vDesk","requires_auth":"none","summary":"An attacker can reveal internal state information via response discrepancies in specific API endpoints of LIVEBOX Collaboration vDesk.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vdesk","vendor":"liveboxcloud"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"An issue was discovered in LIVEBOX Collaboration vDesk through v031. An Observable Response Discrepancy can occur under the /api/v1/vdeskintegration/user/isenableuser endpoint, the /api/v1/sharedsearch?search={NAME]+{SURNAME] endpoint, and the /login endpoint. The web application provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.","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 n/a","id":"CVE-2022-45177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2022-45178"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-45176"},"products":["n/a"],"published":"2024-02-21","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-45173","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-45174","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2022-45172","kev_date_added":null,"published":"2023-01-31"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-45171","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-45178","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":6.5,"headline":"Auth bypass in n/a","id":"CVE-2022-45168","kev_date_added":null,"published":"2024-06-10"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-26","vendors":["n/a"]},"summary":"An attacker can reveal internal state information via response discrepancies in specific API endpoints of LIVEBOX Collaboration vDesk.","url":"https://insights.sbomify.com/CVE-2022-45177/"}