CVE-2026-28224
8.2FirebirdSQL · Firebird
An unauthenticated null pointer dereference vulnerability in Firebird allows remote attackers to crash the database server by sending a crafted packet.
Executive summary
Firebird database servers are vulnerable to a remote denial of service attack due to improper handling of unauthenticated crypt callback packets, which can lead to server crashes.
Vulnerability
The vulnerability is a null pointer dereference (CWE-476) occurring when the server processes an op_crypt_key_callback packet before authentication is completed. This flaw allows an unauthenticated remote attacker to trigger a crash of the database service.
Business impact
The ability for an unauthenticated attacker to remotely crash a database server poses a significant risk to business continuity and service availability. Given the CVSS score of 8.2, this vulnerability is classified as High severity, as it enables total service disruption without requiring user interaction or valid credentials. Organizations relying on Firebird for critical data storage should prioritize this update to prevent downtime and potential operational impact.
Remediation
Immediate Action: Upgrade to Firebird versions 3.0.14, 4.0.7, or 5.0.4, as these releases contain the necessary security fixes for the null pointer dereference.
Proactive Monitoring: Review database error logs and system event logs for unexpected service restarts or instances where the server process terminates abruptly.
Compensating Controls: Implement network-level access control lists or a firewall to restrict access to the Firebird port to authorized IP addresses, thereby reducing the attack surface.
Exploitation status
Public Exploit Available: No (no confirmed weaponized exploit or public proof-of-concept identified).
Analyst recommendation
The severity of this vulnerability stems from the ease with which an attacker can impact system availability without authentication. Administrators must treat this as a high-priority task and apply the vendor-provided patches as soon as possible. Following the update, perform a verification check to ensure the service is running the patched version and that connectivity is restored within the environment.