149 lines
7.4 KiB
JSON
149 lines
7.4 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"dataVersion": "5.1",
|
|
"cveMetadata": {
|
|
"cveId": "CVE-2025-7394",
|
|
"assignerOrgId": "50d2cd11-d01a-48ed-9441-5bfce9d63b27",
|
|
"state": "PUBLISHED",
|
|
"assignerShortName": "wolfSSL",
|
|
"dateReserved": "2025-07-09T16:38:33.567Z",
|
|
"datePublished": "2025-07-18T22:34:23.849Z",
|
|
"dateUpdated": "2025-07-21T15:00:21.780Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"affected": [
|
|
{
|
|
"defaultStatus": "unaffected",
|
|
"product": "wolfSSL",
|
|
"repo": "https://github.com/wolfssl/wolfssl",
|
|
"vendor": "wolfSSL",
|
|
"versions": [
|
|
{
|
|
"lessThanOrEqual": "5.8.0",
|
|
"status": "affected",
|
|
"version": "3.15.0",
|
|
"versionType": "git"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"credits": [
|
|
{
|
|
"lang": "en",
|
|
"type": "finder",
|
|
"value": "Per Allansson"
|
|
}
|
|
],
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"supportingMedia": [
|
|
{
|
|
"base64": false,
|
|
"type": "text/html",
|
|
"value": "<b><span style=\"background-color: transparent;\">In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.</span></b><br>"
|
|
}
|
|
],
|
|
"value": "In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report."
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV4_0": {
|
|
"Automatable": "NOT_DEFINED",
|
|
"Recovery": "NOT_DEFINED",
|
|
"Safety": "NOT_DEFINED",
|
|
"attackComplexity": "HIGH",
|
|
"attackRequirements": "PRESENT",
|
|
"attackVector": "NETWORK",
|
|
"baseScore": 7,
|
|
"baseSeverity": "HIGH",
|
|
"privilegesRequired": "NONE",
|
|
"providerUrgency": "NOT_DEFINED",
|
|
"subAvailabilityImpact": "NONE",
|
|
"subConfidentialityImpact": "HIGH",
|
|
"subIntegrityImpact": "NONE",
|
|
"userInteraction": "PASSIVE",
|
|
"valueDensity": "NOT_DEFINED",
|
|
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
|
|
"version": "4.0",
|
|
"vulnAvailabilityImpact": "NONE",
|
|
"vulnConfidentialityImpact": "HIGH",
|
|
"vulnIntegrityImpact": "NONE",
|
|
"vulnerabilityResponseEffort": "NOT_DEFINED"
|
|
},
|
|
"format": "CVSS",
|
|
"scenarios": [
|
|
{
|
|
"lang": "en",
|
|
"value": "GENERAL"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"cweId": "CWE-200",
|
|
"description": "CWE-200 Exposure of Sensitive Information to an Unauthorized Actor",
|
|
"lang": "en",
|
|
"type": "CWE"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"providerMetadata": {
|
|
"orgId": "50d2cd11-d01a-48ed-9441-5bfce9d63b27",
|
|
"shortName": "wolfSSL",
|
|
"dateUpdated": "2025-07-18T22:57:53.350Z"
|
|
},
|
|
"references": [
|
|
{
|
|
"url": "https://github.com/wolfSSL/wolfssl/blob/master/ChangeLog.md#wolfssl-release-582-july-17-2025"
|
|
}
|
|
],
|
|
"source": {
|
|
"discovery": "EXTERNAL"
|
|
},
|
|
"x_generator": {
|
|
"engine": "Vulnogram 0.2.0"
|
|
}
|
|
},
|
|
"adp": [
|
|
{
|
|
"metrics": [
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"timestamp": "2025-07-21T15:00:11.053980Z",
|
|
"id": "CVE-2025-7394",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "no"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"role": "CISA Coordinator",
|
|
"version": "2.0.3"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2025-07-21T15:00:21.780Z"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
} |