Symmetricom SyncServer S350 2.90.70.3 kernlog.php FileName path traversal

Summaryinfo

A vulnerability was found in Symmetricom SyncServer S100, SyncServer S200, SyncServer S250, SyncServer S300 and SyncServer S350 2.90.70.3. It has been declared as critical. This affects an unknown function of the file kernlog.php. Executing a manipulation of the argument FileName can lead to path traversal. This vulnerability appears as CVE-2020-9032. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability has been found in Symmetricom SyncServer S100, SyncServer S200, SyncServer S250, SyncServer S300 and SyncServer S350 2.90.70.3 and classified as critical. This vulnerability affects some unknown processing of the file kernlog.php. The manipulation of the argument FileName with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to kernlog.php.

The weakness was presented 02/17/2020. This vulnerability was named CVE-2020-9032 since 02/17/2020. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

By approaching the search of inurl:kernlog.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.

See VDB-150270, VDB-150269, VDB-150267 and VDB-150266 for similar entries. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Symmetricom

Name

• SyncServer S100
• SyncServer S200
• SyncServer S250
• SyncServer S300
• SyncServer S350

Version

• 2.90.70.3

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