{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45925 exists.","fix":"No fix has been published for CVE-2022-45925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45925 is a high-severity vulnerability in n/a, published on 18 Jan 2023. 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-45925 and fix it if it is affected.\n\nWhat it is: CVE-2022-45925 is a high-severity vulnerability in n/a, published on 18 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45925 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-45925/ (Markdown: https://insights.sbomify.com/CVE-2022-45925/index.md)","id":"CVE-2022-45925","markdown":"https://insights.sbomify.com/CVE-2022-45925/index.md","name":"CVE-2022-45925","record":{"aliases":["GHSA-2c9x-whr5-j4x3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenText Content Suite","requires_auth":"none","summary":"Attackers can obtain sensitive HTTP headers and CGI variables via the xmlexport action, exposing internal server details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opentext_extended_ecm","vendor":"opentext"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in OpenText Content Suite Platform 22.1 (16.2.19.1803). The action xmlexport accepts the parameter requestContext. If this parameter is present, the response includes most of the HTTP headers sent to the server and some of the CGI variables like remote_adde and server_name, which is an information disclosure.","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":"Information disclosure in n/a","id":"CVE-2022-45925","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2022-45926"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-45924"},"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":"Auth bypass in n/a","id":"CVE-2022-45927","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"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-04-04","vendors":["n/a"]},"summary":"Attackers can obtain sensitive HTTP headers and CGI variables via the xmlexport action, exposing internal server details.","url":"https://insights.sbomify.com/CVE-2022-45925/"}