Adam Tomecek OwnRS 1.2 autor.php ID sql injection

Summaryinfo

A vulnerability marked as critical has been reported in Adam Tomecek OwnRS 1.2. Affected by this vulnerability is an unknown functionality of the file autor.php. The manipulation of the argument ID leads to sql injection. This vulnerability is documented as CVE-2009-0384. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Adam Tomecek OwnRS 1.2 and classified as critical. This issue affects an unknown code of the file autor.php. The manipulation of the argument id 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 autor.php in OwnRS CMS 1.2 allows remote attackers to execute arbitrary SQL commands via the id parameter.

The weakness was released 02/02/2009 (Website). It is possible to read the advisory at milw0rm.com. The identification of this vulnerability is CVE-2009-0384 since 02/02/2009. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

A public exploit has been developed by nuclear and been published even before and not after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:autor.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 vulnerability database at Exploit-DB (7849). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Adam Tomecek

Name

• OwnRS

Version

• 1.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