Use of Externally-Controlled Format String Affecting openvpn-auth-pam-plugin package, versions <2.4.3-5.7.1
Threat Intelligence
Exploit maturity not defined.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Use of Externally-Controlled Format String vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-SLES153-OPENVPNAUTHPAMPLUGIN-2680630
- published14 Apr 2022
- disclosed12 May 2021
Introduced: 12 May 2021
CVE-2018-7544 (opens in a new tab)How to fix?
Upgrade SLES:15.3 openvpn-auth-pam-plugin to version 2.4.3-5.7.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openvpn-auth-pam-plugin package and not the openvpn-auth-pam-plugin package as distributed by SLES.
See How to fix? for SLES:15.3 relevant fixed versions and status.
A cross-protocol scripting issue was discovered in the management interface in OpenVPN through 2.4.5. When this interface is enabled over TCP without a password, and when no other clients are connected to this interface, attackers can execute arbitrary management commands, obtain sensitive information, or cause a denial of service (SIGTERM) by triggering XMLHttpRequest actions in a web browser. This is demonstrated by a multipart/form-data POST to http://localhost:23000 with a "signal SIGTERM" command in a TEXTAREA element. NOTE: The vendor disputes that this is a vulnerability. They state that this is the result of improper configuration of the OpenVPN instance rather than an intrinsic vulnerability, and now more explicitly warn against such configurations in both the management-interface documentation, and with a runtime warning