{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22327 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22327 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22327 is a medium-severity vulnerability in Ibm Urbancode Deploy, published on 1 Apr 2022. 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-22327 and fix it if it is affected.\n\nWhat it is: CVE-2022-22327 is a medium-severity vulnerability in Ibm Urbancode Deploy, published on 1 Apr 2022. 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-22327 in the wild and no public exploit code.\n\nAffected product: Ibm Urbancode Deploy. 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-22327/ (Markdown: https://insights.sbomify.com/CVE-2022-22327/index.md)","id":"CVE-2022-22327","markdown":"https://insights.sbomify.com/CVE-2022-22327/index.md","name":"CVE-2022-22327","record":{"aliases":["GHSA-9gfp-cmrg-hp24"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM UrbanCode Deploy","requires_auth":"none","summary":"Weak cryptographic algorithms in IBM UrbanCode Deploy allow attackers to decrypt highly sensitive information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"urbancode_deploy","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/C:H/I:N/PR:N/AC:H/UI:N/AV:N/S:U/A:N/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM UrbanCode Deploy (UCD) 7.0.5, 7.1.0, 7.1.1, and 7.1.2 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 218859.","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":"Weak cryptography in UrbanCode Deploy","id":"CVE-2022-22327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:urbancode_deploy","products":["ibm:urbancode_deploy"],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in SterlingPartner Engagement Manager","id":"CVE-2022-22328"},"packages":[],"prev":{"headline":"Missing authorization in DataPower Gateway","id":"CVE-2022-22326"},"products":["UrbanCode Deploy"],"published":"2022-04-01","related":[{"cvss_score":10,"headline":"File upload in UrbanCode Deploy","id":"CVE-2016-8938","kev_date_added":null,"published":"2017-02-01"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2014-8900","kev_date_added":null,"published":"2017-08-28"},{"cvss_score":8.2,"headline":"XML external entity in UrbanCode Deploy","id":"CVE-2020-4481","kev_date_added":null,"published":"2020-08-05"},{"cvss_score":8.2,"headline":"Auth bypass in n/a","id":"CVE-2016-0271","kev_date_added":null,"published":"2016-07-08"},{"cvss_score":8.1,"headline":"XML external entity in UrbanCode Deploy","id":"CVE-2017-1149","kev_date_added":null,"published":"2017-04-25"},{"cvss_score":7.7,"headline":"Information disclosure in n/a","id":"CVE-2016-0267","kev_date_added":null,"published":"2016-06-29"},{"cvss_score":7.5,"headline":"Command injection in UrbanCode Deploy","id":"CVE-2016-2942","kev_date_added":null,"published":"2017-02-01"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["IBM"]},"summary":"Weak cryptographic algorithms in IBM UrbanCode Deploy allow attackers to decrypt highly sensitive information.","url":"https://insights.sbomify.com/CVE-2022-22327/"}