{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-33100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-33100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33100 is a medium-severity vulnerability in Ibm Concert, published on 18 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-33100 and fix it if it is affected.\n\nWhat it is: CVE-2025-33100 is a medium-severity vulnerability in Ibm Concert, published on 18 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-33100 in the wild and no public exploit code.\n\nAffected product: Ibm Concert. 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-2025-33100/ (Markdown: https://insights.sbomify.com/CVE-2025-33100/index.md)","id":"CVE-2025-33100","markdown":"https://insights.sbomify.com/CVE-2025-33100/index.md","name":"CVE-2025-33100","record":{"aliases":["GHSA-wfr8-cv9p-f2rv"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Concert Software","requires_auth":"none","summary":"Attackers can exploit hard-coded credentials in IBM Concert Software to access internal data or bypass security controls.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"concert","vendor":"ibm"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"IBM Concert Software 1.0.0 through 1.1.0 \n\ncontains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"IBM Concert Software information disclosure","id":"CVE-2025-33100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:concert","products":["ibm:concert"],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Multiple Vulnerabilities in IBM Concert Software.","id":"CVE-2025-33101"},"packages":[],"prev":{"headline":"IBM Concert Software information disclosure","id":"CVE-2025-33099"},"products":["Concert Software"],"published":"2025-08-18","related":[{"cvss_score":9.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-6721","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-6730","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-6928","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.1,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-3627","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2025-33015","kev_date_added":null,"published":"2026-01-20"},{"cvss_score":7.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-6794","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":7.8,"headline":"Multiple Vulnerabilities in IBM Concert Software","id":"CVE-2026-6935","kev_date_added":null,"published":"2026-09-23"}],"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-08-18","vendors":["IBM"]},"summary":"Attackers can exploit hard-coded credentials in IBM Concert Software to access internal data or bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-33100/"}