Yaeger CMS 1.2.1 File Upload unrestricted upload

Summaryinfo

A vulnerability was found in Yaeger CMS 1.2.1. It has been rated as critical. This affects an unknown function of the component File Upload. Performing a manipulation results in unrestricted upload. This vulnerability is reported as CVE-2015-7571. The attack requires a local approach. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Yaeger CMS 1.2.1 (Content Management System). It has been classified as critical. This affects an unknown function of the component File Upload. The manipulation with an unknown input leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Unrestricted file upload vulnerability in Yeager CMS 1.2.1 allows remote attackers to execute arbitrary code by uploading a file with an executable extension.

The bug was discovered 02/10/2016. The weakness was disclosed 08/07/2017 as EDB-ID 39436 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2015-7571 since 09/29/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1608.002 for this issue.

A public exploit has been developed by SEC Consult and been published even before and not after the advisory. The exploit is shared for download 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 544 days. During that time the estimated underground price was around $0-$5k.

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 (39436). The entries VDB-100530, VDB-100529 and VDB-100531 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Yaeger

Name

• CMS

Version

• 1.2.1

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