Sentrifugo 3.2 html bunitname sql injection

Summaryinfo

A vulnerability was found in Sentrifugo 3.2. It has been classified as critical. Affected by this issue is some unknown functionality of the file through /sentrifugo/index.php/reports/businessunits/format/html. Performing a manipulation of the argument bunitname results in sql injection. This vulnerability is reported as CVE-2024-29873. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Sentrifugo 3.2. It has been classified as critical. This affects an unknown code block of the file through /sentrifugo/index.php/reports/businessunits/format/html. The manipulation of the argument bunitname with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in Sentrifugo 3.2, through /sentrifugo/index.php/reports/businessunits/format/html, 'bunitname' 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 disclosed by Rafael Pedrero. The advisory is shared at incibe.es. This vulnerability is uniquely identified as CVE-2024-29873 since 03/21/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/25/2025). MITRE ATT&CK project uses the attack technique T1505 for this issue.

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Sentrifugo

Version

• 3.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion