Ryneezy phoSheezy 0.2 admin.php header code injection

Summaryinfo

A vulnerability classified as critical has been found in Ryneezy phoSheezy 0.2. Impacted is an unknown function of the file admin.php. The manipulation of the argument header leads to code injection. This vulnerability is listed as CVE-2009-0275. In addition, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Ryneezy phoSheezy 0.2. This issue affects some unknown processing of the file admin.php. The manipulation of the argument header with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Static code injection vulnerability in admin.php in Ryneezy phoSheezy 0.2 allows remote authenticated administrators to inject arbitrary PHP code into config/header via the header parameter. NOTE: this can be exploited by unauthenticated attackers by leveraging CVE-2009-0250. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The weakness was presented 01/14/2009 (Website). The advisory is shared at osvdb.org. The identification of this vulnerability is CVE-2009-0275 since 01/26/2009. The exploitation is known to be easy. The attack may be initiated remotely. Required for exploitation is a simple authentication. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1059 for this issue.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:admin.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 Exploit-DB (7780), OSVDB (51412†) and Secunia (SA33531†). See VDB-46026 and VDB-46025 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Ryneezy

Name

• phoSheezy

Version

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