Octeth Oempro 3.5.5.1 settings_account.php credentials management

Summaryinfo

A vulnerability was found in Octeth Oempro 3.5.5.1. It has been classified as problematic. This affects an unknown part of the file /member/settings_account.php. Performing a manipulation results in credentials management. This vulnerability is reported as CVE-2008-3059. Moreover, an exploit is present. Further authentication should be added.

Detailsinfo

A vulnerability was found in Octeth Oempro 3.5.5.1. It has been classified as problematic. This affects an unknown code block of the file /member/settings_account.php. The manipulation with an unknown input leads to a credentials management vulnerability. CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:

member/settings_account.php in Octeth Oempro 3.5.5.1, and possibly other versions before 4, uses cleartext to transmit a password entered in the FormValue_Password field, which makes it easier for remote attackers to obtain sensitive information by sniffing the network, related to the "Settings - Account Information" tab.

The bug was discovered 07/02/2008. The weakness was disclosed 12/01/2008 (Website). It is possible to read the advisory at osvdb.org. This vulnerability is uniquely identified as CVE-2008-3059 since 07/07/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Technical details and a exploit are known. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

After even before and not, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 143 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:member/settings_account.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 3.5.5.1 eliminates this vulnerability. It is possible to mitigate the problem by adding an authentication mechanism. The best possible mitigation is suggested to be adding authentication. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (47115) and OSVDB (50324†). The entries VDB-45266 and VDB-45265 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Octeth

Name

• Oempro

Version

• 3.5.5.1

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