{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-45178 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-45178 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45178 is a high-severity vulnerability in n/a, published on 14 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45178 and fix it if it is affected.\n\nWhat it is: CVE-2022-45178 is a high-severity vulnerability in n/a, published on 14 Apr 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-2022-45178 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-45178/ (Markdown: https://insights.sbomify.com/CVE-2022-45178/index.md)","id":"CVE-2022-45178","markdown":"https://insights.sbomify.com/CVE-2022-45178/index.md","name":"CVE-2022-45178","record":{"aliases":["GHSA-69vx-3fgc-566q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LIVEBOX Collaboration vDesk","requires_auth":"low_privilege","summary":"A low-privilege SAML user can escalate to administrator or create new users via broken access control in specific API endpoints.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vdesk","vendor":"liveboxcloud"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in LIVEBOX Collaboration vDesk through v018. Broken Access Control exists under the /api/v1/vdeskintegration/saml/user/createorupdate endpoint, the /settings/guest-settings endpoint, the /settings/samlusers-settings endpoint, and the /settings/users-settings endpoint. A malicious user (already logged in as a SAML User) is able to achieve privilege escalation from a low-privilege user (FGM user) to an administrative user (GGU user), including the administrator, or create new users even without an admin role.","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":"Privilege escalation in n/a","id":"CVE-2022-45178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-45179"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-45177"},"products":["n/a"],"published":"2023-04-14","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":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-45177","kev_date_added":null,"published":"2024-02-21"},{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-07","vendors":["n/a"]},"summary":"A low-privilege SAML user can escalate to administrator or create new users via broken access control in specific API endpoints.","url":"https://insights.sbomify.com/CVE-2022-45178/"}