hitCode hitAppoint 4.4.3 index.php Username sql injection

Summaryinfo

A vulnerability has been found in hitCode hitAppoint 4.4.3 and classified as critical. This affects an unknown part of the file index.php. Performing a manipulation of the argument Username results in sql injection. This vulnerability was named CVE-2011-5038. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in hitCode hitAppoint 4.4.3. This affects an unknown part of the file index.php. The manipulation of the argument username 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 hitCode hitAppoint 4.5.17 and possibly earlier allows remote attackers to execute arbitrary SQL commands via the username parameter to index.php. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The weakness was presented 12/30/2011 (Website). The advisory is shared at osvdb.org. This vulnerability is uniquely identified as CVE-2011-5038 since 12/30/2011. 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. MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.

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

The vulnerability is also documented in the databases at X-Force (71740), OSVDB (77580†) and Secunia (SA47140†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• hitCode

Name

• hitAppoint

Version

• 4.4.3

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion