{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45927 exists.","fix":"No fix has been published for CVE-2022-45927 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45927 is a high-severity authentication bypass vulnerability in n/a, published on 18 Jan 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-45927 and fix it if it is affected.\n\nWhat it is: CVE-2022-45927 is a high-severity authentication bypass vulnerability in n/a, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45927 exists.\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-45927/ (Markdown: https://insights.sbomify.com/CVE-2022-45927/index.md)","id":"CVE-2022-45927","markdown":"https://insights.sbomify.com/CVE-2022-45927/index.md","name":"CVE-2022-45927","record":{"aliases":["GHSA-rp59-mwr6-m562"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Content Management System","requires_auth":"low_privilege","summary":"Attackers can bypass authentication on QDS endpoints to create objects and execute arbitrary code on the Content Server.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opentext_extended_ecm","vendor":"opentext"}],"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":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An issue was discovered in OpenText Content Suite Platform 22.1 (16.2.19.1803). The Java application server can be used to bypass the authentication of the QDS endpoints of the Content Server. These endpoints can be used to create objects and execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2022-45927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2022-45928"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2022-45926"},"products":["n/a"],"published":"2023-01-18","related":[{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2022-45922","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2022-45923","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-45926","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2022-45928","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2022-45924","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-45925","kev_date_added":null,"published":"2023-01-18"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-04","vendors":["n/a"]},"summary":"Attackers can bypass authentication on QDS endpoints to create objects and execute arbitrary code on the Content Server.","url":"https://insights.sbomify.com/CVE-2022-45927/"}