{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-3425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-3425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3425 is a medium-severity vulnerability in broker, published on 1 Jun 2021. 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-2021-3425 and fix it if it is affected.\n\nWhat it is: CVE-2021-3425 is a medium-severity vulnerability in broker, published on 1 Jun 2021. 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-2021-3425 in the wild and no public exploit code.\n\nAffected product: broker. 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-2021-3425/ (Markdown: https://insights.sbomify.com/CVE-2021-3425/index.md)","id":"CVE-2021-3425","markdown":"https://insights.sbomify.com/CVE-2021-3425/index.md","name":"CVE-2021-3425","record":{"aliases":["GHSA-4h8h-q487-wmvf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AMQ Broker","requires_auth":"high_privilege","summary":"Attackers can read encrypted JDBC credentials from AMQ Broker logs when using JDBC persistence, exposing sensitive database access information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"jboss_a-mq","vendor":"redhat"}],"cvss":{"score":4.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"A flaw was found in the AMQ Broker that discloses JDBC encrypted usernames and passwords when provided in the AMQ Broker application logfile when using the jdbc persistence functionality. Versions shipped in Red Hat AMQ 7 are vulnerable.","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":"Information disclosure in broker","id":"CVE-2021-3425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in python","id":"CVE-2021-3426"},"packages":[],"prev":{"headline":"Keycloak is vulnerable to IDN homograph attack","id":"CVE-2021-3424"},"products":["broker"],"published":"2021-06-01","related":[{"cvss_score":7.2,"headline":"Deserialization in Karaf","id":"CVE-2016-8648","kev_date_added":null,"published":"2018-08-01"},{"cvss_score":5.6,"headline":"XML external entity in Red Hat AMQ","id":"CVE-2020-14379","kev_date_added":null,"published":"2022-08-16"},{"cvss_score":5.5,"headline":"Operator: passwords defined in secrets shown in statefulset yaml","id":"CVE-2023-4066","kev_date_added":null,"published":"2023-09-27"},{"cvss_score":5.5,"headline":"Operator: plaintext password in operator log","id":"CVE-2023-4065","kev_date_added":null,"published":"2023-09-26"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2015-5181","kev_date_added":null,"published":"2017-09-25"},{"cvss_score":5.3,"headline":"Deserialization in Fuse","id":"CVE-2016-8653","kev_date_added":null,"published":"2018-08-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-08-03","vendors":["n/a"]},"summary":"Attackers can read encrypted JDBC credentials from AMQ Broker logs when using JDBC persistence, exposing sensitive database access information.","url":"https://insights.sbomify.com/CVE-2021-3425/"}