{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38389 is a high-severity vulnerability in IBM Tivoli Workload Scheduler, published on 2 Feb 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-38389 and fix it if it is affected.\n\nWhat it is: CVE-2022-38389 is a high-severity vulnerability in IBM Tivoli Workload Scheduler, published on 2 Feb 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-38389 in the wild and no public exploit code.\n\nAffected product: IBM Tivoli Workload Scheduler. 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-38389/ (Markdown: https://insights.sbomify.com/CVE-2022-38389/index.md)","id":"CVE-2022-38389","markdown":"https://insights.sbomify.com/CVE-2022-38389/index.md","name":"CVE-2022-38389","record":{"aliases":["GHSA-r788-hfmg-5r69"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Workload Scheduler","requires_auth":"low_privilege","summary":"Remote attackers can exploit XML processing flaws in IBM Tivoli Workload Scheduler to expose sensitive data or cause memory exhaustion.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"tivoli_workload_scheduler","vendor":"ibm"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"IBM Tivoli Workload Scheduler 9.4, 9.5, and 10.1 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.  IBM X-Force ID:  233975.","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":"IBM Tivoli Workload Scheduler XML external entity injection","id":"CVE-2022-38389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Business Automation Workflow","id":"CVE-2022-38390"},"packages":[],"prev":{"headline":"Information disclosure in Navigator Mobile","id":"CVE-2022-38388"},"products":["Tivoli Workload Scheduler"],"published":"2023-02-02","related":[{"cvss_score":10,"headline":"IBM Tivoli Workload Scheduler XML external entity injection","id":"CVE-2022-22486","kev_date_added":null,"published":"2023-02-02"},{"cvss_score":8.4,"headline":"Privilege escalation in Workload Scheduler Distributed","id":"CVE-2019-4031","kev_date_added":null,"published":"2019-10-16"},{"cvss_score":7.4,"headline":"Privilege escalation in Workload Scheduler","id":"CVE-2018-1386","kev_date_added":null,"published":"2018-03-14"},{"cvss_score":5.9,"headline":"Memory corruption in Workload Scheduler","id":"CVE-2021-20349","kev_date_added":null,"published":"2021-08-09"},{"cvss_score":5.4,"headline":"Cross-site scripting in Workload Scheduler","id":"CVE-2019-4608","kev_date_added":null,"published":"2020-03-10"},{"cvss_score":3.3,"headline":"Information disclosure in Tivoli Workload Scheduler","id":"CVE-2017-1716","kev_date_added":null,"published":"2017-12-13"}],"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-03-25","vendors":["IBM"]},"summary":"Remote attackers can exploit XML processing flaws in IBM Tivoli Workload Scheduler to expose sensitive data or cause memory exhaustion.","url":"https://insights.sbomify.com/CVE-2022-38389/"}