SeaCMS up to 6.61 adm1n/admin_database.php bakfiles path traversal

Summaryinfo

A vulnerability marked as critical has been reported in SeaCMS up to 6.61. This impacts an unknown function of the file adm1n/admin_database.php. Performing a manipulation of the argument bakfiles as part of Directory results in path traversal. This vulnerability is identified as CVE-2018-16446. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in SeaCMS up to 6.61. This affects an unknown code of the file adm1n/admin_database.php. The manipulation of the argument bakfiles as part of a Directory leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on integrity, and availability. The summary by CVE is:

An issue was discovered in SeaCMS through 6.61. adm1n/admin_database.php allows remote attackers to delete arbitrary files via directory traversal sequences in the bakfiles parameter. This can allow the product to be reinstalled by deleting install_lock.txt.

The bug was discovered 08/09/2018. The weakness was released 09/04/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-16446 since 09/03/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

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

Entries connected to this vulnerability are available at VDB-123560 and VDB-123559. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Name

• SeaCMS

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9
• 6.10
• 6.11
• 6.12
• 6.13
• 6.14
• 6.15
• 6.16
• 6.17
• 6.18
• 6.19
• 6.20
• 6.21
• 6.22
• 6.23
• 6.24
• 6.25
• 6.26
• 6.27
• 6.28
• 6.29
• 6.30
• 6.31
• 6.32
• 6.33
• 6.34
• 6.35
• 6.36
• 6.37
• 6.38
• 6.39
• 6.40
• 6.41
• 6.42
• 6.43
• 6.44
• 6.45
• 6.46
• 6.47
• 6.48
• 6.49
• 6.50
• 6.51
• 6.52
• 6.53
• 6.54
• 6.55
• 6.56
• 6.57
• 6.58
• 6.59
• 6.60
• 6.61

License

• free

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