openssl on Windows built with openssldir set from the build machine (Uncontrolled Search Path Element)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| microsoft | vcpkg | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Microsoft | Vcpkg |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.743% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft
Microsoft vcpkg |
|
| Vendors & Products |
Microsoft
Microsoft vcpkg |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vcpkg is a free and open-source C/C++ package manager. Prior to version 3.6.1#3, vcpkg's Windows builds of OpenSSL set openssldir to a path on the build machine, making that path be attackable later on customer machines. This issue has been patched in version 3.6.1#3. | |
| Title | openssl on Windows built with openssldir set from the build machine (Uncontrolled Search Path Element) | |
| Weaknesses | CWE-427 | |
| References |
| |
| Metrics |
cvssV3_1
|