vendor:
Anchor CMS
by:
Tijme Gommers
9.8
CVSS
CRITICAL
Information Disclosure
200
CWE
Product Name: Anchor CMS
Affected Version From: 0.12.3a
Affected Version To: 0.12.3a
Patch Exists: YES
Related CWE: CVE-2018-7251
CPE: anchorcms
Tags: cve,cve2018,anchorcms,logs,error,packetstorm
CVSS Metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Nuclei References:
https://github.com/anchorcms/anchor-cms/issues/1247, https://twitter.com/finnwea/status/965279233030393856, http://packetstormsecurity.com/files/154723/Anchor-CMS-0.12.3a-Information-Disclosure.html, https://github.com/anchorcms/anchor-cms/releases/tag/0.12.7, https://nvd.nist.gov/vuln/detail/CVE-2018-7251
Nuclei Metadata: {'max-request': 1, 'vendor': 'anchorcms', 'product': 'anchor'}
Platforms Tested: Linux
2019
Information disclosure (MySQL password) in error log
By default, AnchorCMS will log errors to the "/anchor/errors.log" file in the webroot of the web application. This allows malicious users to access the error log and view potentially sensitive information. Sometimes the AnchorCMS error log contains occurrences of the MySQL error "Can't connect to MySQL server on 'xxx.xxx.xxx.xxx' (111)". When this error occurs the variables of the MySQL connector class are serialized into a JSON object and logged to the error log.
Mitigation:
To mitigate this vulnerability, ensure that the error log file is not accessible to unauthorized users. This can be done by configuring proper file permissions and access controls.