{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-24975 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-24975 is a high-severity authentication bypass vulnerability in FirebirdSQL firebird, published on 15 Aug 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-24975 and fix it if it is affected.\n\nWhat it is: CVE-2025-24975 is a high-severity authentication bypass vulnerability in FirebirdSQL firebird, published on 15 Aug 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-24975 in the wild and no public exploit code.\n\nAffected product: FirebirdSQL firebird. 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-24975/ (Markdown: https://insights.sbomify.com/CVE-2025-24975/index.md)","id":"CVE-2025-24975","markdown":"https://insights.sbomify.com/CVE-2025-24975/index.md","name":"CVE-2025-24975","record":{"aliases":["DEBIAN-CVE-2025-24975","GHSA-fx9r-rj68-7p69","UBUNTU-CVE-2025-24975"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Firebird relational database","requires_auth":"low_privilege","summary":"Attackers can access encrypted databases without keys or cause server crashes due to improper connection pool verification in Firebird.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"firebird","vendor":"firebirdsql"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"Firebird is a relational database. Prior to snapshot versions 4.0.6.3183, 5.0.2.1610, and 6.0.0.609, Firebird is vulnerable if ExtConnPoolSize is not set equal to 0. If connections stored in ExtConnPool are not verified for presence and suitability of the CryptCallback interface is used when created versus what is available could result in a segfault in the server process. Encrypted databases, accessed by execute statement on external, may be accessed later by an attachment missing a key to that database. In a case when execute statement are chained, segfault may happen. Additionally, the segfault may affect unencrypted databases. This issue has been patched in snapshot versions 4.0.6.3183, 5.0.2.1610, and 6.0.0.609 and point releases 4.0.6 and 5.0.2. A workaround for this issue involves setting ExtConnPoolSize equal to 0 in firebird.conf.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Firebird Non-Authorized Access to Encrypted Database Using Execute Statement on External","id":"CVE-2025-24975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Distribution's token authentication allows attacker to inject an untrusted signing key in a JWT","id":"CVE-2025-24976"},"packages":[],"prev":{"headline":"DataEase Mysql JDBC Connection Parameters Not Being Verified Leads to Arbitrary File Read Vulnerability","id":"CVE-2025-24974"},"products":["firebird"],"published":"2025-08-15","related":[{"cvss_score":10,"headline":"Firebird: Path Traversal + Arbitrary File Write Leads to Remote Code Execution","id":"CVE-2026-40342","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0467","kev_date_added":null,"published":"2008-01-29"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-4992","kev_date_added":null,"published":"2007-10-11"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-5245","kev_date_added":null,"published":"2007-10-06"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-5246","kev_date_added":null,"published":"2007-10-06"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2017-6369","kev_date_added":null,"published":"2017-03-24"},{"cvss_score":8.2,"headline":"Firebird has Pre-Auth DOS when Processing Out of Order CNCT_specific_data Segments","id":"CVE-2026-27890","kev_date_added":null,"published":"2026-04-17"}],"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-20","vendors":["FirebirdSQL"]},"summary":"Attackers can access encrypted databases without keys or cause server crashes due to improper connection pool verification in Firebird.","url":"https://insights.sbomify.com/CVE-2025-24975/"}