Sentrifugo 3.2 add agencyids sql injection

Summaryinfo

A vulnerability was found in Sentrifugo 3.2. It has been rated as critical. This vulnerability affects unknown code of the file through /sentrifugo/index.php/empscreening/add. The manipulation of the argument agencyids leads to sql injection. This vulnerability is traded as CVE-2024-29872. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Sentrifugo 3.2. It has been rated as critical. This issue affects an unknown function of the file through /sentrifugo/index.php/empscreening/add. The manipulation of the argument agencyids with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in Sentrifugo 3.2, through /sentrifugo/index.php/empscreening/add, 'agencyids' parameter. The exploitation of this vulnerability could allow a remote user to send a specially crafted query to the server and extract all the data from it.

The weakness was shared by Rafael Pedrero. It is possible to read the advisory at incibe.es. The identification of this vulnerability is CVE-2024-29872 since 03/21/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/25/2025). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Sentrifugo

Version

• 3.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion