{"dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": {"cveId": "CVE-2024-4741", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "state": "PUBLISHED", "assignerShortName": "openssl", "dateReserved": "2024-05-10T09:56:11.310Z", "datePublished": "2024-11-13T10:20:50.711Z", "dateUpdated": "2024-11-13T14:49:05.977Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "OpenSSL", "vendor": "OpenSSL", "versions": [{"lessThan": "3.3.1", "status": "affected", "version": "3.3.0", "versionType": "semver"}, {"lessThan": "3.2.2", "status": "affected", "version": "3.2.0", "versionType": "semver"}, {"lessThan": "3.1.6", "status": "affected", "version": "3.1.0", "versionType": "semver"}, {"lessThan": "3.0.14", "status": "affected", "version": "3.0.0", "versionType": "semver"}, {"lessThan": "1.1.1y", "status": "affected", "version": "1.1.1", "versionType": "custom"}]}], "credits": [{"lang": "en", "type": "finder", "value": "William Ahern (Akamai)"}, {"lang": "en", "type": "remediation developer", "value": "Matt Caswell"}, {"lang": "en", "type": "remediation developer", "value": "Watson Ladd (Akamai)"}], "datePublic": "2024-05-27T23:00:00.000Z", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause<br>memory to be accessed that was previously freed in some situations<br><br>Impact summary: A use after free can have a range of potential consequences such<br>as the corruption of valid data, crashes or execution of arbitrary code.<br>However, only applications that directly call the SSL_free_buffers function are<br>affected by this issue. Applications that do not call this function are not<br>vulnerable. Our investigations indicate that this function is rarely used by<br>applications.<br><br>The SSL_free_buffers function is used to free the internal OpenSSL buffer used<br>when processing an incoming record from the network. The call is only expected<br>to succeed if the buffer is not currently in use. However, two scenarios have<br>been identified where the buffer is freed even when still in use.<br><br>The first scenario occurs where a record header has been received from the<br>network and processed by OpenSSL, but the full record body has not yet arrived.<br>In this case calling SSL_free_buffers will succeed even though a record has only<br>been partially processed and the buffer is still in use.<br><br>The second scenario occurs where a full record containing application data has<br>been received and processed by OpenSSL but the application has only read part of<br>this data. Again a call to SSL_free_buffers will succeed even though the buffer<br>is still in use.<br><br>While these scenarios could occur accidentally during normal operation a<br>malicious attacker could attempt to engineer a stituation where this occurs.<br>We are not aware of this issue being actively exploited.<br><br>The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}], "value": "Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause\nmemory to be accessed that was previously freed in some situations\n\nImpact summary: A use after free can have a range of potential consequences such\nas the corruption of valid data, crashes or execution of arbitrary code.\nHowever, only applications that directly call the SSL_free_buffers function are\naffected by this issue. Applications that do not call this function are not\nvulnerable. Our investigations indicate that this function is rarely used by\napplications.\n\nThe SSL_free_buffers function is used to free the internal OpenSSL buffer used\nwhen processing an incoming record from the network. The call is only expected\nto succeed if the buffer is not currently in use. However, two scenarios have\nbeen identified where the buffer is freed even when still in use.\n\nThe first scenario occurs where a record header has been received from the\nnetwork and processed by OpenSSL, but the full record body has not yet arrived.\nIn this case calling SSL_free_buffers will succeed even though a record has only\nbeen partially processed and the buffer is still in use.\n\nThe second scenario occurs where a full record containing application data has\nbeen received and processed by OpenSSL but the application has only read part of\nthis data. Again a call to SSL_free_buffers will succeed even though the buffer\nis still in use.\n\nWhile these scenarios could occur accidentally during normal operation a\nmalicious attacker could attempt to engineer a stituation where this occurs.\nWe are not aware of this issue being actively exploited.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}], "metrics": [{"format": "other", "other": {"content": {"text": "Low"}, "type": "https://www.openssl.org/policies/secpolicy.html"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-416", "description": "CWE-416 Use After Free", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2024-11-13T10:20:50.711Z"}, "references": [{"name": "OpenSSL Advisory", "tags": ["vendor-advisory"], "url": "https://www.openssl.org/news/secadv/20240528.txt"}, {"name": "3.3.1 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8"}, {"name": "3.2.2 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac"}, {"name": "3.1.6 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177"}, {"name": "3.0.14 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d"}, {"name": "1.1.1y git commit", "tags": ["patch"], "url": "https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4"}], "source": {"discovery": "UNKNOWN"}, "title": "Use After Free with SSL_free_buffers", "x_generator": {"engine": "Vulnogram 0.2.0"}}, "adp": [{"affected": [{"vendor": "openssl", "product": "openssl", "cpes": ["cpe:2.3:a:openssl:openssl:-:*:*:*:*:*:*:*"], "defaultStatus": "unknown", "versions": [{"version": "1.1.1", "status": "affected", "lessThan": "1.1.1y", "versionType": "semver"}, {"version": "3.0.0", "status": "affected", "lessThan": "3.0.14", "versionType": "semver"}, {"version": "3.1.0", "status": "affected", "lessThan": "3.1.6", "versionType": "semver"}, {"version": "3.2.0", "status": "affected", "lessThan": "3.2.2", "versionType": "semver"}, {"version": "3.3.0", "status": "affected", "lessThan": "3.3.1", "versionType": "semver"}]}], "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}}, {"other": {"type": "ssvc", "content": {"timestamp": "2024-11-13T14:45:07.092438Z", "id": "CVE-2024-4741", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"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": "2024-11-13T14:49:05.977Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}}, {"other": {"type": "ssvc", "content": {"id": "CVE-2024-4741", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-11-13T14:45:07.092438Z"}}}], "affected": [{"cpes": ["cpe:2.3:a:openssl:openssl:-:*:*:*:*:*:*:*"], "vendor": "openssl", "product": "openssl", "versions": [{"status": "affected", "version": "1.1.1", "lessThan": "1.1.1y", "versionType": "semver"}, {"status": "affected", "version": "3.0.0", "lessThan": "3.0.14", "versionType": "semver"}, {"status": "affected", "version": "3.1.0", "lessThan": "3.1.6", "versionType": "semver"}, {"status": "affected", "version": "3.2.0", "lessThan": "3.2.2", "versionType": "semver"}, {"status": "affected", "version": "3.3.0", "lessThan": "3.3.1", "versionType": "semver"}], "defaultStatus": "unknown"}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-11-13T14:48:43.735Z"}}], "cna": {"title": "Use After Free with SSL_free_buffers", "source": {"discovery": "UNKNOWN"}, "credits": [{"lang": "en", "type": "finder", "value": "William Ahern (Akamai)"}, {"lang": "en", "type": "remediation developer", "value": "Matt Caswell"}, {"lang": "en", "type": "remediation developer", "value": "Watson Ladd (Akamai)"}], "metrics": [{"other": {"type": "https://www.openssl.org/policies/secpolicy.html", "content": {"text": "Low"}}, "format": "other"}], "affected": [{"vendor": "OpenSSL", "product": "OpenSSL", "versions": [{"status": "affected", "version": "3.3.0", "lessThan": "3.3.1", "versionType": "semver"}, {"status": "affected", "version": "3.2.0", "lessThan": "3.2.2", "versionType": "semver"}, {"status": "affected", "version": "3.1.0", "lessThan": "3.1.6", "versionType": "semver"}, {"status": "affected", "version": "3.0.0", "lessThan": "3.0.14", "versionType": "semver"}, {"status": "affected", "version": "1.1.1", "lessThan": "1.1.1y", "versionType": "custom"}], "defaultStatus": "unaffected"}], "datePublic": "2024-05-27T23:00:00.000Z", "references": [{"url": "https://www.openssl.org/news/secadv/20240528.txt", "name": "OpenSSL Advisory", "tags": ["vendor-advisory"]}, {"url": "https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8", "name": "3.3.1 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac", "name": "3.2.2 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177", "name": "3.1.6 git commit", "tags": ["patch"]}, {"url": "https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d", "name": "3.0.14 git commit", "tags": ["patch"]}, {"url": "https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4", "name": "1.1.1y git commit", "tags": ["patch"]}], "x_generator": {"engine": "Vulnogram 0.2.0"}, "descriptions": [{"lang": "en", "value": "Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause\nmemory to be accessed that was previously freed in some situations\n\nImpact summary: A use after free can have a range of potential consequences such\nas the corruption of valid data, crashes or execution of arbitrary code.\nHowever, only applications that directly call the SSL_free_buffers function are\naffected by this issue. Applications that do not call this function are not\nvulnerable. Our investigations indicate that this function is rarely used by\napplications.\n\nThe SSL_free_buffers function is used to free the internal OpenSSL buffer used\nwhen processing an incoming record from the network. The call is only expected\nto succeed if the buffer is not currently in use. However, two scenarios have\nbeen identified where the buffer is freed even when still in use.\n\nThe first scenario occurs where a record header has been received from the\nnetwork and processed by OpenSSL, but the full record body has not yet arrived.\nIn this case calling SSL_free_buffers will succeed even though a record has only\nbeen partially processed and the buffer is still in use.\n\nThe second scenario occurs where a full record containing application data has\nbeen received and processed by OpenSSL but the application has only read part of\nthis data. Again a call to SSL_free_buffers will succeed even though the buffer\nis still in use.\n\nWhile these scenarios could occur accidentally during normal operation a\nmalicious attacker could attempt to engineer a stituation where this occurs.\nWe are not aware of this issue being actively exploited.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "supportingMedia": [{"type": "text/html", "value": "Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause<br>memory to be accessed that was previously freed in some situations<br><br>Impact summary: A use after free can have a range of potential consequences such<br>as the corruption of valid data, crashes or execution of arbitrary code.<br>However, only applications that directly call the SSL_free_buffers function are<br>affected by this issue. Applications that do not call this function are not<br>vulnerable. Our investigations indicate that this function is rarely used by<br>applications.<br><br>The SSL_free_buffers function is used to free the internal OpenSSL buffer used<br>when processing an incoming record from the network. The call is only expected<br>to succeed if the buffer is not currently in use. However, two scenarios have<br>been identified where the buffer is freed even when still in use.<br><br>The first scenario occurs where a record header has been received from the<br>network and processed by OpenSSL, but the full record body has not yet arrived.<br>In this case calling SSL_free_buffers will succeed even though a record has only<br>been partially processed and the buffer is still in use.<br><br>The second scenario occurs where a full record containing application data has<br>been received and processed by OpenSSL but the application has only read part of<br>this data. Again a call to SSL_free_buffers will succeed even though the buffer<br>is still in use.<br><br>While these scenarios could occur accidentally during normal operation a<br>malicious attacker could attempt to engineer a stituation where this occurs.<br>We are not aware of this issue being actively exploited.<br><br>The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-416", "description": "CWE-416 Use After Free"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2024-11-13T10:20:50.711Z"}}}, "cveMetadata": {"cveId": "CVE-2024-4741", "state": "PUBLISHED", "dateUpdated": "2024-11-13T14:49:05.977Z", "dateReserved": "2024-05-10T09:56:11.310Z", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "datePublished": "2024-11-13T10:20:50.711Z", "assignerShortName": "openssl"}, "dataVersion": "5.1"}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause\nmemory to be accessed that was previously freed in some situations\n\nImpact summary: A use after free can have a range of potential consequences such\nas the corruption of valid data, crashes or execution of arbitrary code.\nHowever, only applications that directly call the SSL_free_buffers function are\naffected by this issue. Applications that do not call this function are not\nvulnerable. Our investigations indicate that this function is rarely used by\napplications.\n\nThe SSL_free_buffers function is used to free the internal OpenSSL buffer used\nwhen processing an incoming record from the network. The call is only expected\nto succeed if the buffer is not currently in use. However, two scenarios have\nbeen identified where the buffer is freed even when still in use.\n\nThe first scenario occurs where a record header has been received from the\nnetwork and processed by OpenSSL, but the full record body has not yet arrived.\nIn this case calling SSL_free_buffers will succeed even though a record has only\nbeen partially processed and the buffer is still in use.\n\nThe second scenario occurs where a full record containing application data has\nbeen received and processed by OpenSSL but the application has only read part of\nthis data. Again a call to SSL_free_buffers will succeed even though the buffer\nis still in use.\n\nWhile these scenarios could occur accidentally during normal operation a\nmalicious attacker could attempt to engineer a stituation where this occurs.\nWe are not aware of this issue being actively exploited.\n\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."}], "id": "CVE-2024-4741", "lastModified": "2024-11-13T17:01:16.850", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "type": "Secondary"}]}, "published": "2024-11-13T11:15:04.480", "references": [{"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8"}, {"source": "openssl-security@openssl.org", "url": "https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4"}, {"source": "openssl-security@openssl.org", "url": "https://www.openssl.org/news/secadv/20240528.txt"}], "sourceIdentifier": "openssl-security@openssl.org", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-416"}], "source": "openssl-security@openssl.org", "type": "Secondary"}]}

{"affected_release": [{"advisory": "RHSA-2024:9333", "cpe": "cpe:/a:redhat:enterprise_linux:9", "package": "openssl-1:3.2.2-6.el9_5", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2024-11-12T00:00:00Z"}, {"advisory": "RHSA-2024:9333", "cpe": "cpe:/o:redhat:enterprise_linux:9", "package": "openssl-1:3.2.2-6.el9_5", "product_name": "Red Hat Enterprise Linux 9", "release_date": "2024-11-12T00:00:00Z"}], "bugzilla": {"description": "openssl: Use After Free with SSL_free_buffers", "id": "2283757", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2283757"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.6", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L", "status": "verified"}, "cwe": "CWE-416", "details": ["Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause\nmemory to be accessed that was previously freed in some situations\nImpact summary: A use after free can have a range of potential consequences such\nas the corruption of valid data, crashes or execution of arbitrary code.\nHowever, only applications that directly call the SSL_free_buffers function are\naffected by this issue. Applications that do not call this function are not\nvulnerable. Our investigations indicate that this function is rarely used by\napplications.\nThe SSL_free_buffers function is used to free the internal OpenSSL buffer used\nwhen processing an incoming record from the network. The call is only expected\nto succeed if the buffer is not currently in use. However, two scenarios have\nbeen identified where the buffer is freed even when still in use.\nThe first scenario occurs where a record header has been received from the\nnetwork and processed by OpenSSL, but the full record body has not yet arrived.\nIn this case calling SSL_free_buffers will succeed even though a record has only\nbeen partially processed and the buffer is still in use.\nThe second scenario occurs where a full record containing application data has\nbeen received and processed by OpenSSL but the application has only read part of\nthis data. Again a call to SSL_free_buffers will succeed even though the buffer\nis still in use.\nWhile these scenarios could occur accidentally during normal operation a\nmalicious attacker could attempt to engineer a stituation where this occurs.\nWe are not aware of this issue being actively exploited.\nThe FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.", "A use-after-free vulnerability was found in OpenSSL. Calling the OpenSSL API SSL_free_buffers function may cause memory to be accessed that was previously freed in some situations."], "mitigation": {"lang": "en:us", "value": "Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability."}, "name": "CVE-2024-4741", "package_state": [{"cpe": "cpe:/a:redhat:logging:5", "fix_state": "Affected", "package_name": "openshift-logging/fluentd-rhel8", "product_name": "Logging Subsystem for Red Hat OpenShift"}, {"cpe": "cpe:/a:redhat:red_hat_3scale_amp:2", "fix_state": "Affected", "package_name": "3scale-amp-backend-container", "product_name": "Red Hat 3scale API Management Platform 2"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Fix deferred", "package_name": "ovmf", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "compat-openssl10", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "edk2", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "mingw-openssl", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Fix deferred", "package_name": "openssl", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "shim", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "shim-unsigned-x64", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "compat-openssl11", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Fix deferred", "package_name": "edk2", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "shim", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "shim-unsigned-aarch64", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "shim-unsigned-x64", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/a:redhat:jboss_core_services:1", "fix_state": "Affected", "package_name": "openssl", "product_name": "Red Hat JBoss Core Services"}, {"cpe": "cpe:/a:redhat:jboss_enterprise_web_server:5", "fix_state": "Affected", "package_name": "openssl", "product_name": "Red Hat JBoss Web Server 5"}], "public_date": "2024-05-28T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2024-4741\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-4741\nhttps://www.openssl.org/news/secadv/20240528.txt"], "statement": "Red Hat classifies this vulnerability as having a low impact because the affected function is infrequently used by applications. However, Red Hat includes this function in their regular packages, which is why the related components are listed as affected in the table below.", "threat_severity": "Low", "upstream_fix": "openssl 3.3.1, openssl 3.2.2, openssl 3.1.6, openssl 3.0.14, openssl 1.1.1y"}