CyberSecBulletin
CVE-2022-26651NVD status: Modified

Asterisk: Improper Neutralization of Special Elements used in an SQL Command

Published Updated By the CyberSecBulletin desk

CVE-2022-26651 is a critical-severity improper neutralization of special elements used in an SQL command vulnerability in Asterisk from Digium, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 16.25.2, 18.11.2, 19.3.2 as the first without the flaw, so updating Asterisk to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 7.03% chance of exploitation within 30 days, which is in the top 5.72% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Asterisk to 16.25.2 or 18.11.2 or 19.3.2, whichever matches your release line, or a later version.
  2. Read the advisory on packetstormsecurity.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
DigiumAsterisk16.0.0 up to, but not including, 16.25.2; 18.0 up to, but not including, 18.11.2; 19.0.0 up to, but not including, 19.3.216.25.2, 18.11.2, 19.3.2
DigiumCertified Asterisk16.8Not stated
DebianDebian Linux10.0; 11.0Not stated

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalNVD
CVSS 2.07.5HighNVD

Official description

An issue was discovered in Asterisk through 19.x and Certified Asterisk through 16.8-cert13. The func_odbc module provides possibly inadequate escaping functionality for backslash characters in SQL queries, resulting in user-provided data creating a broken SQL query or possibly a SQL injection. This is fixed in 16.25.2, 18.11.2, and 19.3.2, and 16.8-cert14.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Special Elements used in an SQL Command

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

How developers prevent this class of flaw

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.

More Improper Neutralization of Special Elements used in an SQL Command vulnerabilities (CWE-89)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in Asterisk

All Asterisk vulnerabilities

Recent Improper Neutralization of Special Elements used in an SQL Command vulnerabilities

Spotted an error? Tell us.