Summary
Several vulnerabilities have been discovered in the LibGit2Sharp or underlying LibGit2 library.This open-source component is widely used in a lot of products worldwide.The product is vulnerable to remote code execution, privilege escalation and tampering.PLCnext Engineer is using the LibGit2Sharp library to provide version control capabilities.
Details
Impact
Availability, integrity, or confidentiality of PLCnext Engineer might be compromised by attacks exploiting these vulnerabilities. Specially crafted git configuration files lead to a remote code execution which enables the attacker to elevate privileges and obtain access to the application. The attacker may take over the system, steal data or prevent a system or application from running correctly.
Mitigation
To mitigate aforementioned vulnerabilities the integrity and authenticity of the git configuration data must be ensured. Otherwise, we kindly advise you to refrain from using the version control feature in version lower than 2023.6
Remediation
Update PLCnext Engineer to 2023.6.
Vulnerabilities 11
-
High 7.8
Bypass of safe.directory protections in Git
Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported …
-
Medium 6.0CVE-2022-24765 Public exploit
Uncontrolled search for the Git directory in Git for Windows
Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users working on multi-user machines, where untrusted parties have write access to the same hard disk. Those untrusted parties could create the folder `C:\.git`, …
-
Unscored —
In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remot…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
-
Unscored —CVE-2019-1349 EPSS 34%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —CVE-2019-1350 EPSS 26%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —CVE-2019-1351 Public exploit
A tampering vulnerability exists when Git for Visual Studio improperly handles virtual drive paths, aka 'Git for Visual…
-
Unscored —CVE-2019-1352 EPSS 24%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
-
Unscored —CVE-2019-1354 EPSS 23%
A remote code execution vulnerability exists when Git for Visual Studio improperly sanitizes input, aka 'Git for Visual…
-
Unscored —
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15…
Revision history
-
#2
Fix: quotation mark
-
#1
Initial revision.
References
-
VDE-2023-016: Phoenix Contact: PLCnext Engineer Vulnerabilities in LibGit2Sharp/LibGit2 - HTML
https://certvde.com/en/advisories/VDE-2023-016/
-
Vendor PSIRT
https://phoenixcontact.com/psirt
-
CERT@VDE Security Advisories for Phoenix Contact GmbH & Co. KG
https://certvde.com/en/advisories/vendor/phoenixcontact/