{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34319 is a medium-severity vulnerability in IBM CICS TX, published on 14 Nov 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-34319 and fix it if it is affected.\n\nWhat it is: CVE-2022-34319 is a medium-severity vulnerability in IBM CICS TX, published on 14 Nov 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-34319 in the wild and no public exploit code.\n\nAffected product: IBM CICS TX. 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-34319/ (Markdown: https://insights.sbomify.com/CVE-2022-34319/index.md)","id":"CVE-2022-34319","markdown":"https://insights.sbomify.com/CVE-2022-34319/index.md","name":"CVE-2022-34319","record":{"aliases":["GHSA-5f74-2734-278c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM CICS TX","requires_auth":"none","summary":"Weak cryptographic algorithms in IBM CICS TX 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":"cics_tx","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM CICS TX 11.7 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.  IBM X-Force ID:  229463.","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 CICS TX information disclosure","id":"CVE-2022-34319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"IBM CICS TX information disclosure","id":"CVE-2022-34320"},"packages":[],"prev":{"headline":"IBM CICS TX clickjacking","id":"CVE-2022-34318"},"products":["CICS TX"],"published":"2022-11-14","related":[{"cvss_score":9.8,"headline":"Command injection in CICS TX Advanced","id":"CVE-2022-31767","kev_date_added":null,"published":"2022-06-24"},{"cvss_score":7.8,"headline":"IBM CICS TX code execution","id":"CVE-2025-1329","kev_date_added":null,"published":"2025-05-08"},{"cvss_score":7.8,"headline":"IBM CICS TX code execution","id":"CVE-2025-1330","kev_date_added":null,"published":"2025-05-08"},{"cvss_score":7.8,"headline":"IBM CICS TX code execution","id":"CVE-2025-1331","kev_date_added":null,"published":"2025-05-08"},{"cvss_score":7.5,"headline":"IBM GSKit-Crypto information disclosure","id":"CVE-2023-33850","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":7.2,"headline":"IBM CICS TX cross-site scripting","id":"CVE-2024-41746","kev_date_added":null,"published":"2025-01-16"},{"cvss_score":6.5,"headline":"IBM CICS TX Standard cross-site request forgery","id":"CVE-2024-41744","kev_date_added":null,"published":"2024-11-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["IBM"]},"summary":"Weak cryptographic algorithms in IBM CICS TX allow attackers to decrypt highly sensitive information.","url":"https://insights.sbomify.com/CVE-2022-34319/"}