3CX, a VoIP communications firm, has advised customers to disable SQL Database integrations due to the risks posed by a potential vulnerability.
A SQL Injection vulnerability in 3CX CRM Integration has been identified as CVE-2023-49954.
An attacker can manipulate an application’s database queries due to SQL Injection, a prevalent yet harmful web security flaw.
This may result in attackers gaining access to sensitive data and, in extreme circumstances, in full control of the database.
The vulnerability targets the CRM integration templates that 3CX offers for connecting to different databases, including MsSQL, PostgreSQL, MongoDB, and MySQL.
“If one of the Integration templates has been used (MsSQL, MySQL, PostgreSQL) they can be subject to SQL injection attacks if the 3CX server is available on the internet and no Web application firewall is in front of the 3CX machine. In that case, it is possible to manipulate the original SQL query executed against a database”, according to 3CX CEO Nick Galea.
“Customers using MongoDB or any of our web-based CRM integration templates are not affected by this.”
Disable your SQL Database Integrations
Pierre Jourdan, the chief information security officer at 3CX, said today that “if you are using SQL Database integration, it’s subject potentially to vulnerability – depending upon the configuration.”
“As a precautionary measure, and whilst we work on a solution to safely re-enable this integration.”
Temporarily disable the following database integrations:
- Database MongoDB
- Database MsSQL
- Database MySQL
- Database PostgreSQL
There is no impact on any web-based CRM integrations.
Which 3CX Versions are affected?
Verify whether you’re using one of the above-mentioned integrations if you’re running Version 18.
This can be accomplished via Management Console / Settings / CRM. Set it to “None” and save.
Verify whether you are using any of the above-mentioned integrations if you are running Version 20.
You can accomplish this from Webclient / Admin Console / Integrations / CRM. Save it with “None” selected.
The report also stated that merely 0.25% of the user population has integrated sequel. This is an older integration designed for an on-premise firewall-secured network.
However, depending on the configuration, employing a SQL Database integration may expose you to a vulnerability. Customers are being asked to disable SQL database integrations to prevent hacking attacks.