YzmCMS up to 3.7 forgotten-password reset_email.html information disclosure

Summaryinfo

A vulnerability described as problematic has been identified in YzmCMS up to 3.7. This affects an unknown part of the file index.php/member/reset/reset_email.html of the component forgotten-password. The manipulation results in information disclosure. This vulnerability is identified as CVE-2018-11554. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in YzmCMS up to 3.7. Affected is an unknown code block of the file index.php/member/reset/reset_email.html of the component forgotten-password. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

The forgotten-password feature in index.php/member/reset/reset_email.html in YzmCMS v3.2 through v3.7 has a Response Discrepancy Information Exposure issue and an unexpectedly long lifetime for a verification code, which makes it easier for remote attackers to hijack accounts via a brute-force approach.

The bug was discovered 06/02/2018. The weakness was released 06/05/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2018-11554 since 05/29/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:index.php/member/reset/reset_email.html 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.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• YzmCMS

Version

• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7

License

• commercial

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion