{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-33012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-33012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33012 is a medium-severity authentication bypass vulnerability in Ibm Db2, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-33012 and fix it if it is affected.\n\nWhat it is: CVE-2025-33012 is a medium-severity authentication bypass vulnerability in Ibm Db2, published on 7 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-33012 in the wild and no public exploit code.\n\nAffected product: Ibm Db2. 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-33012/ (Markdown: https://insights.sbomify.com/CVE-2025-33012/index.md)","id":"CVE-2025-33012","markdown":"https://insights.sbomify.com/CVE-2025-33012/index.md","name":"CVE-2025-33012","record":{"aliases":["GHSA-fgjg-3fmq-57hw"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Db2 database","requires_auth":"low_privilege","summary":"An authenticated user can regain access to an IBM Db2 database after account lockout by using an expired password, bypassing security controls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"db2","vendor":"ibm"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-324","name":"Use of a Key Past its Expiration Date"}],"description":"IBM Db2 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux could allow an authenticated user to regain access after account lockout due to password use after expiration date.","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 Db2 improper account lockout","id":"CVE-2025-33012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:db2","products":["ibm:db2"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"IBM MQ Operator information disclosure","id":"CVE-2025-33013"},"packages":[],"prev":{"headline":"IBM Sterling B2B Integrator and IBM Sterling File Gateway cross-site scripting","id":"CVE-2025-33008"},"products":["Db2"],"published":"2025-11-07","related":[{"cvss_score":10,"headline":"IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors.","id":"CVE-2012-1797","kev_date_added":null,"published":"2012-03-20"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-3731","kev_date_added":null,"published":"2010-10-05"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-3193","kev_date_added":null,"published":"2010-08-31"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-4335","kev_date_added":null,"published":"2009-12-16"},{"cvss_score":10,"headline":"Missing authorization in n/a","id":"CVE-2009-3473","kev_date_added":null,"published":"2009-09-29"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2008-6820","kev_date_added":null,"published":"2009-06-03"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-6821","kev_date_added":null,"published":"2009-06-03"}],"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-11-07","vendors":["IBM"]},"summary":"An authenticated user can regain access to an IBM Db2 database after account lockout by using an expired password, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2025-33012/"}