{
  "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi",
  "issues" : [
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-d4db9c53",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-11187: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file\u000a\u000aFor additional help see: **Vulnerability CVE-2025-11187**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)|\u000a\u000aIssue summary: PBMAC1 parameters in PKCS#12 files are missing validation\u000awhich can trigger a stack-based buffer overflow, invalid pointer or NULL\u000apointer dereference during MAC verification.\u000a\u000aImpact summary: The stack buffer overflow or NULL pointer dereference may\u000acause a crash leading to Denial of Service for an application that parses\u000auntrusted PKCS#12 files. The buffer overflow may also potentially enable\u000acode execution depending on platform mitigations.\u000a\u000aWhen verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2\u000asalt and keylength parameters from the file are used without validation.\u000aIf the value of keylength exceeds the size of the fixed stack buffer used\u000afor the derived key (64 bytes), the key derivation will overflow the buffer.\u000aThe overflow length is attacker-controlled. Also, if the salt parameter is\u000anot an OCTET STRING type this can lead to invalid or NULL pointer\u000adereference.\u000a\u000aExploiting this issue requires a user or application to process\u000aa maliciously crafted PKCS#12 file. It is uncommon to accept untrusted\u000aPKCS#12 files in applications as they are usually used to store private\u000akeys which are trusted by definition. For this reason the issue was assessed\u000aas Moderate severity.\u000a\u000aThe FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as\u000aPKCS#12 processing is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.\u000a\u000aOpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do\u000anot support PBMAC1 in PKCS#12.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-11187\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-11187: : CVE-2025-11187: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file\u000a\u000aFor additional help see: **Vulnerability CVE-2025-11187**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)|\u000a\u000aIssue summary: PBMAC1 parameters in PKCS#12 files are missing validation\u000awhich can trigger a stack-based buffer overflow, invalid pointer or NULL\u000apointer dereference during MAC verification.\u000a\u000aImpact summary: The stack buffer overflow or NULL pointer dereference may\u000acause a crash leading to Denial of Service for an application that parses\u000auntrusted PKCS#12 files. The buffer overflow may also potentially enable\u000acode execution depending on platform mitigations.\u000a\u000aWhen verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2\u000asalt and keylength parameters from the file are used without validation.\u000aIf the value of keylength exceeds the size of the fixed stack buffer used\u000afor the derived key (64 bytes), the key derivation will overflow the buffer.\u000aThe overflow length is attacker-controlled. Also, if the salt parameter is\u000anot an OCTET STRING type this can lead to invalid or NULL pointer\u000adereference.\u000a\u000aExploiting this issue requires a user or application to process\u000aa maliciously crafted PKCS#12 file. It is uncommon to accept untrusted\u000aPKCS#12 files in applications as they are usually used to store private\u000akeys which are trusted by definition. For this reason the issue was assessed\u000aas Moderate severity.\u000a\u000aThe FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as\u000aPKCS#12 processing is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.\u000a\u000aOpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do\u000anot support PBMAC1 in PKCS#12.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-11187\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)",
      "type" : "CVE-2025-11187"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-d4db9c53",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-11187: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file\u000a\u000aFor additional help see: **Vulnerability CVE-2025-11187**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)|\u000a\u000aIssue summary: PBMAC1 parameters in PKCS#12 files are missing validation\u000awhich can trigger a stack-based buffer overflow, invalid pointer or NULL\u000apointer dereference during MAC verification.\u000a\u000aImpact summary: The stack buffer overflow or NULL pointer dereference may\u000acause a crash leading to Denial of Service for an application that parses\u000auntrusted PKCS#12 files. The buffer overflow may also potentially enable\u000acode execution depending on platform mitigations.\u000a\u000aWhen verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2\u000asalt and keylength parameters from the file are used without validation.\u000aIf the value of keylength exceeds the size of the fixed stack buffer used\u000afor the derived key (64 bytes), the key derivation will overflow the buffer.\u000aThe overflow length is attacker-controlled. Also, if the salt parameter is\u000anot an OCTET STRING type this can lead to invalid or NULL pointer\u000adereference.\u000a\u000aExploiting this issue requires a user or application to process\u000aa maliciously crafted PKCS#12 file. It is uncommon to accept untrusted\u000aPKCS#12 files in applications as they are usually used to store private\u000akeys which are trusted by definition. For this reason the issue was assessed\u000aas Moderate severity.\u000a\u000aThe FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as\u000aPKCS#12 processing is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.\u000a\u000aOpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do\u000anot support PBMAC1 in PKCS#12.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-11187\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-11187: : CVE-2025-11187: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution or denial of service through crafted PKCS#12 file\u000a\u000aFor additional help see: **Vulnerability CVE-2025-11187**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)|\u000a\u000aIssue summary: PBMAC1 parameters in PKCS#12 files are missing validation\u000awhich can trigger a stack-based buffer overflow, invalid pointer or NULL\u000apointer dereference during MAC verification.\u000a\u000aImpact summary: The stack buffer overflow or NULL pointer dereference may\u000acause a crash leading to Denial of Service for an application that parses\u000auntrusted PKCS#12 files. The buffer overflow may also potentially enable\u000acode execution depending on platform mitigations.\u000a\u000aWhen verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2\u000asalt and keylength parameters from the file are used without validation.\u000aIf the value of keylength exceeds the size of the fixed stack buffer used\u000afor the derived key (64 bytes), the key derivation will overflow the buffer.\u000aThe overflow length is attacker-controlled. Also, if the salt parameter is\u000anot an OCTET STRING type this can lead to invalid or NULL pointer\u000adereference.\u000a\u000aExploiting this issue requires a user or application to process\u000aa maliciously crafted PKCS#12 file. It is uncommon to accept untrusted\u000aPKCS#12 files in applications as they are usually used to store private\u000akeys which are trusted by definition. For this reason the issue was assessed\u000aas Moderate severity.\u000a\u000aThe FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as\u000aPKCS#12 processing is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.\u000a\u000aOpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do\u000anot support PBMAC1 in PKCS#12.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-11187\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-11187](https://avd.aquasec.com/nvd/cve-2025-11187)",
      "type" : "CVE-2025-11187"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-c9a061fe",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-13151: OsPackageVulnerability\u000a\u000alibtasn1: libtasn1: Denial of Service via stack-based buffer overflow in asn1_expend_octet_string\u000a\u000aFor additional help see: **Vulnerability CVE-2025-13151**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libtasn1|4.21.0-r0|[CVE-2025-13151](https://avd.aquasec.com/nvd/cve-2025-13151)|\u000a\u000aStack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.\u000a\u000aPackage: libtasn1\u000aInstalled Version: 4.20.0-r0\u000aVulnerability CVE-2025-13151\u000aSeverity: MEDIUM\u000aFixed Version: 4.21.0-r0\u000aLink: [CVE-2025-13151](https://avd.aquasec.com/nvd/cve-2025-13151)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-13151: : CVE-2025-13151: OsPackageVulnerability\u000a\u000alibtasn1: libtasn1: Denial of Service via stack-based buffer overflow in asn1_expend_octet_string\u000a\u000aFor additional help see: **Vulnerability CVE-2025-13151**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libtasn1|4.21.0-r0|[CVE-2025-13151](https://avd.aquasec.com/nvd/cve-2025-13151)|\u000a\u000aStack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.\u000a\u000aPackage: libtasn1\u000aInstalled Version: 4.20.0-r0\u000aVulnerability CVE-2025-13151\u000aSeverity: MEDIUM\u000aFixed Version: 4.21.0-r0\u000aLink: [CVE-2025-13151](https://avd.aquasec.com/nvd/cve-2025-13151)",
      "type" : "CVE-2025-13151"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-edb135c7",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15467: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS parsing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15467**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|libssl3|3.5.5-r0|[CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)|\u000a\u000aIssue summary: Parsing CMS AuthEnvelopedData message with maliciously\u000acrafted AEAD parameters can trigger a stack buffer overflow.\u000a\u000aImpact summary: A stack buffer overflow may lead to a crash, causing Denial\u000aof Service, or potentially remote code execution.\u000a\u000aWhen parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as\u000aAES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is\u000acopied into a fixed-size stack buffer without verifying that its length fits\u000athe destination. An attacker can supply a crafted CMS message with an\u000aoversized IV, causing a stack-based out-of-bounds write before any\u000aauthentication or tag verification occurs.\u000a\u000aApplications and services that parse untrusted CMS or PKCS#7 content using\u000aAEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.\u000aBecause the overflow occurs prior to authentication, no valid key material\u000ais required to trigger it. While exploitability to remote code execution\u000adepends on platform and toolchain mitigations, the stack-based write\u000aprimitive represents a severe risk.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the CMS implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.\u000a\u000aOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15467\u000aSeverity: CRITICAL\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2025-15467: : CVE-2025-15467: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS parsing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15467**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|libssl3|3.5.5-r0|[CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)|\u000a\u000aIssue summary: Parsing CMS AuthEnvelopedData message with maliciously\u000acrafted AEAD parameters can trigger a stack buffer overflow.\u000a\u000aImpact summary: A stack buffer overflow may lead to a crash, causing Denial\u000aof Service, or potentially remote code execution.\u000a\u000aWhen parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as\u000aAES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is\u000acopied into a fixed-size stack buffer without verifying that its length fits\u000athe destination. An attacker can supply a crafted CMS message with an\u000aoversized IV, causing a stack-based out-of-bounds write before any\u000aauthentication or tag verification occurs.\u000a\u000aApplications and services that parse untrusted CMS or PKCS#7 content using\u000aAEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.\u000aBecause the overflow occurs prior to authentication, no valid key material\u000ais required to trigger it. While exploitability to remote code execution\u000adepends on platform and toolchain mitigations, the stack-based write\u000aprimitive represents a severe risk.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the CMS implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.\u000a\u000aOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15467\u000aSeverity: CRITICAL\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)",
      "type" : "CVE-2025-15467"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-edb135c7",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15467: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS parsing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15467**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|libssl3|3.5.5-r0|[CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)|\u000a\u000aIssue summary: Parsing CMS AuthEnvelopedData message with maliciously\u000acrafted AEAD parameters can trigger a stack buffer overflow.\u000a\u000aImpact summary: A stack buffer overflow may lead to a crash, causing Denial\u000aof Service, or potentially remote code execution.\u000a\u000aWhen parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as\u000aAES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is\u000acopied into a fixed-size stack buffer without verifying that its length fits\u000athe destination. An attacker can supply a crafted CMS message with an\u000aoversized IV, causing a stack-based out-of-bounds write before any\u000aauthentication or tag verification occurs.\u000a\u000aApplications and services that parse untrusted CMS or PKCS#7 content using\u000aAEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.\u000aBecause the overflow occurs prior to authentication, no valid key material\u000ais required to trigger it. While exploitability to remote code execution\u000adepends on platform and toolchain mitigations, the stack-based write\u000aprimitive represents a severe risk.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the CMS implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.\u000a\u000aOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15467\u000aSeverity: CRITICAL\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2025-15467: : CVE-2025-15467: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS parsing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15467**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|CRITICAL|libssl3|3.5.5-r0|[CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)|\u000a\u000aIssue summary: Parsing CMS AuthEnvelopedData message with maliciously\u000acrafted AEAD parameters can trigger a stack buffer overflow.\u000a\u000aImpact summary: A stack buffer overflow may lead to a crash, causing Denial\u000aof Service, or potentially remote code execution.\u000a\u000aWhen parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as\u000aAES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is\u000acopied into a fixed-size stack buffer without verifying that its length fits\u000athe destination. An attacker can supply a crafted CMS message with an\u000aoversized IV, causing a stack-based out-of-bounds write before any\u000aauthentication or tag verification occurs.\u000a\u000aApplications and services that parse untrusted CMS or PKCS#7 content using\u000aAEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.\u000aBecause the overflow occurs prior to authentication, no valid key material\u000ais required to trigger it. While exploitability to remote code execution\u000adepends on platform and toolchain mitigations, the stack-based write\u000aprimitive represents a severe risk.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\u000aissue, as the CMS implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.\u000a\u000aOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15467\u000aSeverity: CRITICAL\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15467](https://avd.aquasec.com/nvd/cve-2025-15467)",
      "type" : "CVE-2025-15467"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-fc162b5",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15468: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15468**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)|\u000a\u000aIssue summary: If an application using the SSL_CIPHER_find() function in\u000aa QUIC protocol client or server receives an unknown cipher suite from\u000athe peer, a NULL dereference occurs.\u000a\u000aImpact summary: A NULL pointer dereference leads to abnormal termination of\u000athe running process causing Denial of Service.\u000a\u000aSome applications call SSL_CIPHER_find() from the client_hello_cb callback\u000aon the cipher ID received from the peer. If this is done with an SSL object\u000aimplementing the QUIC protocol, NULL pointer dereference will happen if\u000athe examined cipher ID is unknown or unsupported.\u000a\u000aAs it is not very common to call this function in applications using the QUIC \u000aprotocol and the worst outcome is Denial of Service, the issue was assessed\u000aas Low severity.\u000a\u000aThe vulnerable code was introduced in the 3.2 version with the addition\u000aof the QUIC protocol support.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the QUIC implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15468\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-15468: : CVE-2025-15468: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15468**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)|\u000a\u000aIssue summary: If an application using the SSL_CIPHER_find() function in\u000aa QUIC protocol client or server receives an unknown cipher suite from\u000athe peer, a NULL dereference occurs.\u000a\u000aImpact summary: A NULL pointer dereference leads to abnormal termination of\u000athe running process causing Denial of Service.\u000a\u000aSome applications call SSL_CIPHER_find() from the client_hello_cb callback\u000aon the cipher ID received from the peer. If this is done with an SSL object\u000aimplementing the QUIC protocol, NULL pointer dereference will happen if\u000athe examined cipher ID is unknown or unsupported.\u000a\u000aAs it is not very common to call this function in applications using the QUIC \u000aprotocol and the worst outcome is Denial of Service, the issue was assessed\u000aas Low severity.\u000a\u000aThe vulnerable code was introduced in the 3.2 version with the addition\u000aof the QUIC protocol support.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the QUIC implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15468\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)",
      "type" : "CVE-2025-15468"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-fc162b5",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15468: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15468**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)|\u000a\u000aIssue summary: If an application using the SSL_CIPHER_find() function in\u000aa QUIC protocol client or server receives an unknown cipher suite from\u000athe peer, a NULL dereference occurs.\u000a\u000aImpact summary: A NULL pointer dereference leads to abnormal termination of\u000athe running process causing Denial of Service.\u000a\u000aSome applications call SSL_CIPHER_find() from the client_hello_cb callback\u000aon the cipher ID received from the peer. If this is done with an SSL object\u000aimplementing the QUIC protocol, NULL pointer dereference will happen if\u000athe examined cipher ID is unknown or unsupported.\u000a\u000aAs it is not very common to call this function in applications using the QUIC \u000aprotocol and the worst outcome is Denial of Service, the issue was assessed\u000aas Low severity.\u000a\u000aThe vulnerable code was introduced in the 3.2 version with the addition\u000aof the QUIC protocol support.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the QUIC implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15468\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-15468: : CVE-2025-15468: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via NULL pointer dereference in QUIC protocol handling\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15468**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)|\u000a\u000aIssue summary: If an application using the SSL_CIPHER_find() function in\u000aa QUIC protocol client or server receives an unknown cipher suite from\u000athe peer, a NULL dereference occurs.\u000a\u000aImpact summary: A NULL pointer dereference leads to abnormal termination of\u000athe running process causing Denial of Service.\u000a\u000aSome applications call SSL_CIPHER_find() from the client_hello_cb callback\u000aon the cipher ID received from the peer. If this is done with an SSL object\u000aimplementing the QUIC protocol, NULL pointer dereference will happen if\u000athe examined cipher ID is unknown or unsupported.\u000a\u000aAs it is not very common to call this function in applications using the QUIC \u000aprotocol and the worst outcome is Denial of Service, the issue was assessed\u000aas Low severity.\u000a\u000aThe vulnerable code was introduced in the 3.2 version with the addition\u000aof the QUIC protocol support.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the QUIC implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15468\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15468](https://avd.aquasec.com/nvd/cve-2025-15468)",
      "type" : "CVE-2025-15468"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-fddfba6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15469: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15469**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)|\u000a\u000aIssue summary: The 'openssl dgst' command-line tool silently truncates input\u000adata to 16MB when using one-shot signing algorithms and reports success instead\u000aof an error.\u000a\u000aImpact summary: A user signing or verifying files larger than 16MB with\u000aone-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\u000afile is authenticated while trailing data beyond 16MB remains unauthenticated.\u000a\u000aWhen the 'openssl dgst' command is used with algorithms that only support\u000aone-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\u000ais buffered with a 16MB limit. If the input exceeds this limit, the tool\u000asilently truncates to the first 16MB and continues without signaling an error,\u000acontrary to what the documentation states. This creates an integrity gap where\u000atrailing bytes can be modified without detection if both signing and\u000averification are performed using the same affected codepath.\u000a\u000aThe issue affects only the command-line tool behavior. Verifiers that process\u000athe full message using library APIs will reject the signature, so the risk\u000aprimarily affects workflows that both sign and verify with the affected\u000a'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\u000alibrary users are unaffected.\u000a\u000aThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\u000acommand-line tools are outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.5 and 3.6 are vulnerable to this issue.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15469\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-15469: : CVE-2025-15469: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15469**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)|\u000a\u000aIssue summary: The 'openssl dgst' command-line tool silently truncates input\u000adata to 16MB when using one-shot signing algorithms and reports success instead\u000aof an error.\u000a\u000aImpact summary: A user signing or verifying files larger than 16MB with\u000aone-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\u000afile is authenticated while trailing data beyond 16MB remains unauthenticated.\u000a\u000aWhen the 'openssl dgst' command is used with algorithms that only support\u000aone-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\u000ais buffered with a 16MB limit. If the input exceeds this limit, the tool\u000asilently truncates to the first 16MB and continues without signaling an error,\u000acontrary to what the documentation states. This creates an integrity gap where\u000atrailing bytes can be modified without detection if both signing and\u000averification are performed using the same affected codepath.\u000a\u000aThe issue affects only the command-line tool behavior. Verifiers that process\u000athe full message using library APIs will reject the signature, so the risk\u000aprimarily affects workflows that both sign and verify with the affected\u000a'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\u000alibrary users are unaffected.\u000a\u000aThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\u000acommand-line tools are outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.5 and 3.6 are vulnerable to this issue.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15469\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)",
      "type" : "CVE-2025-15469"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-fddfba6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-15469: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15469**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)|\u000a\u000aIssue summary: The 'openssl dgst' command-line tool silently truncates input\u000adata to 16MB when using one-shot signing algorithms and reports success instead\u000aof an error.\u000a\u000aImpact summary: A user signing or verifying files larger than 16MB with\u000aone-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\u000afile is authenticated while trailing data beyond 16MB remains unauthenticated.\u000a\u000aWhen the 'openssl dgst' command is used with algorithms that only support\u000aone-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\u000ais buffered with a 16MB limit. If the input exceeds this limit, the tool\u000asilently truncates to the first 16MB and continues without signaling an error,\u000acontrary to what the documentation states. This creates an integrity gap where\u000atrailing bytes can be modified without detection if both signing and\u000averification are performed using the same affected codepath.\u000a\u000aThe issue affects only the command-line tool behavior. Verifiers that process\u000athe full message using library APIs will reject the signature, so the risk\u000aprimarily affects workflows that both sign and verify with the affected\u000a'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\u000alibrary users are unaffected.\u000a\u000aThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\u000acommand-line tools are outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.5 and 3.6 are vulnerable to this issue.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15469\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-15469: : CVE-2025-15469: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Data integrity bypass in `openssl dgst` command due to silent truncation\u000a\u000aFor additional help see: **Vulnerability CVE-2025-15469**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)|\u000a\u000aIssue summary: The 'openssl dgst' command-line tool silently truncates input\u000adata to 16MB when using one-shot signing algorithms and reports success instead\u000aof an error.\u000a\u000aImpact summary: A user signing or verifying files larger than 16MB with\u000aone-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\u000afile is authenticated while trailing data beyond 16MB remains unauthenticated.\u000a\u000aWhen the 'openssl dgst' command is used with algorithms that only support\u000aone-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\u000ais buffered with a 16MB limit. If the input exceeds this limit, the tool\u000asilently truncates to the first 16MB and continues without signaling an error,\u000acontrary to what the documentation states. This creates an integrity gap where\u000atrailing bytes can be modified without detection if both signing and\u000averification are performed using the same affected codepath.\u000a\u000aThe issue affects only the command-line tool behavior. Verifiers that process\u000athe full message using library APIs will reject the signature, so the risk\u000aprimarily affects workflows that both sign and verify with the affected\u000a'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\u000alibrary users are unaffected.\u000a\u000aThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\u000acommand-line tools are outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.5 and 3.6 are vulnerable to this issue.\u000a\u000aOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-15469\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-15469](https://avd.aquasec.com/nvd/cve-2025-15469)",
      "type" : "CVE-2025-15469"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-cac4b8c4",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-66199: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate compression\u000a\u000aFor additional help see: **Vulnerability CVE-2025-66199**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)|\u000a\u000aIssue summary: A TLS 1.3 connection using certificate compression can be\u000aforced to allocate a large buffer before decompression without checking\u000aagainst the configured certificate size limit.\u000a\u000aImpact summary: An attacker can cause per-connection memory allocations of\u000aup to approximately 22 MiB and extra CPU work, potentially leading to\u000aservice degradation or resource exhaustion (Denial of Service).\u000a\u000aIn affected configurations, the peer-supplied uncompressed certificate\u000alength from a CompressedCertificate message is used to grow a heap buffer\u000aprior to decompression. This length is not bounded by the max_cert_list\u000asetting, which otherwise constrains certificate message sizes. An attacker\u000acan exploit this to cause large per-connection allocations followed by\u000ahandshake failure. No memory corruption or information disclosure occurs.\u000a\u000aThis issue only affects builds where TLS 1.3 certificate compression is\u000acompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\u000aalgorithm (brotli, zlib, or zstd) is available, and where the compression\u000aextension is negotiated. Both clients receiving a server CompressedCertificate\u000aand servers in mutual TLS scenarios receiving a client CompressedCertificate\u000aare affected. Servers that do not request client certificates are not\u000avulnerable to client-initiated attacks.\u000a\u000aUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\u000ato disable receiving compressed certificates.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the TLS implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-66199\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-66199: : CVE-2025-66199: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate compression\u000a\u000aFor additional help see: **Vulnerability CVE-2025-66199**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)|\u000a\u000aIssue summary: A TLS 1.3 connection using certificate compression can be\u000aforced to allocate a large buffer before decompression without checking\u000aagainst the configured certificate size limit.\u000a\u000aImpact summary: An attacker can cause per-connection memory allocations of\u000aup to approximately 22 MiB and extra CPU work, potentially leading to\u000aservice degradation or resource exhaustion (Denial of Service).\u000a\u000aIn affected configurations, the peer-supplied uncompressed certificate\u000alength from a CompressedCertificate message is used to grow a heap buffer\u000aprior to decompression. This length is not bounded by the max_cert_list\u000asetting, which otherwise constrains certificate message sizes. An attacker\u000acan exploit this to cause large per-connection allocations followed by\u000ahandshake failure. No memory corruption or information disclosure occurs.\u000a\u000aThis issue only affects builds where TLS 1.3 certificate compression is\u000acompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\u000aalgorithm (brotli, zlib, or zstd) is available, and where the compression\u000aextension is negotiated. Both clients receiving a server CompressedCertificate\u000aand servers in mutual TLS scenarios receiving a client CompressedCertificate\u000aare affected. Servers that do not request client certificates are not\u000avulnerable to client-initiated attacks.\u000a\u000aUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\u000ato disable receiving compressed certificates.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the TLS implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-66199\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)",
      "type" : "CVE-2025-66199"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-cac4b8c4",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-66199: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate compression\u000a\u000aFor additional help see: **Vulnerability CVE-2025-66199**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)|\u000a\u000aIssue summary: A TLS 1.3 connection using certificate compression can be\u000aforced to allocate a large buffer before decompression without checking\u000aagainst the configured certificate size limit.\u000a\u000aImpact summary: An attacker can cause per-connection memory allocations of\u000aup to approximately 22 MiB and extra CPU work, potentially leading to\u000aservice degradation or resource exhaustion (Denial of Service).\u000a\u000aIn affected configurations, the peer-supplied uncompressed certificate\u000alength from a CompressedCertificate message is used to grow a heap buffer\u000aprior to decompression. This length is not bounded by the max_cert_list\u000asetting, which otherwise constrains certificate message sizes. An attacker\u000acan exploit this to cause large per-connection allocations followed by\u000ahandshake failure. No memory corruption or information disclosure occurs.\u000a\u000aThis issue only affects builds where TLS 1.3 certificate compression is\u000acompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\u000aalgorithm (brotli, zlib, or zstd) is available, and where the compression\u000aextension is negotiated. Both clients receiving a server CompressedCertificate\u000aand servers in mutual TLS scenarios receiving a client CompressedCertificate\u000aare affected. Servers that do not request client certificates are not\u000avulnerable to client-initiated attacks.\u000a\u000aUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\u000ato disable receiving compressed certificates.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the TLS implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-66199\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-66199: : CVE-2025-66199: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to excessive memory allocation in TLS 1.3 certificate compression\u000a\u000aFor additional help see: **Vulnerability CVE-2025-66199**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)|\u000a\u000aIssue summary: A TLS 1.3 connection using certificate compression can be\u000aforced to allocate a large buffer before decompression without checking\u000aagainst the configured certificate size limit.\u000a\u000aImpact summary: An attacker can cause per-connection memory allocations of\u000aup to approximately 22 MiB and extra CPU work, potentially leading to\u000aservice degradation or resource exhaustion (Denial of Service).\u000a\u000aIn affected configurations, the peer-supplied uncompressed certificate\u000alength from a CompressedCertificate message is used to grow a heap buffer\u000aprior to decompression. This length is not bounded by the max_cert_list\u000asetting, which otherwise constrains certificate message sizes. An attacker\u000acan exploit this to cause large per-connection allocations followed by\u000ahandshake failure. No memory corruption or information disclosure occurs.\u000a\u000aThis issue only affects builds where TLS 1.3 certificate compression is\u000acompiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression\u000aalgorithm (brotli, zlib, or zstd) is available, and where the compression\u000aextension is negotiated. Both clients receiving a server CompressedCertificate\u000aand servers in mutual TLS scenarios receiving a client CompressedCertificate\u000aare affected. Servers that do not request client certificates are not\u000avulnerable to client-initiated attacks.\u000a\u000aUsers can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION\u000ato disable receiving compressed certificates.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,\u000aas the TLS implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.\u000a\u000aOpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-66199\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-66199](https://avd.aquasec.com/nvd/cve-2025-66199)",
      "type" : "CVE-2025-66199"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-bf33b39c",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68160: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68160**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)|\u000a\u000aIssue summary: Writing large, newline-free data into a BIO chain using the\u000aline-buffering filter where the next BIO performs short writes can trigger\u000aa heap-based out-of-bounds write.\u000a\u000aImpact summary: This out-of-bounds write can cause memory corruption which\u000atypically results in a crash, leading to Denial of Service for an application.\u000a\u000aThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\u000aTLS/SSL data paths. In OpenSSL command-line applications, it is typically\u000aonly pushed onto stdout/stderr on VMS systems. Third-party applications that\u000aexplicitly use this filter with a BIO chain that can short-write and that\u000awrite large, newline-free data influenced by an attacker would be affected.\u000aHowever, the circumstances where this could happen are unlikely to be under\u000aattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\u000adata controlled by an attacker. For that reason the issue was assessed as\u000aLow severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the BIO implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-68160\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-68160: : CVE-2025-68160: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68160**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)|\u000a\u000aIssue summary: Writing large, newline-free data into a BIO chain using the\u000aline-buffering filter where the next BIO performs short writes can trigger\u000aa heap-based out-of-bounds write.\u000a\u000aImpact summary: This out-of-bounds write can cause memory corruption which\u000atypically results in a crash, leading to Denial of Service for an application.\u000a\u000aThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\u000aTLS/SSL data paths. In OpenSSL command-line applications, it is typically\u000aonly pushed onto stdout/stderr on VMS systems. Third-party applications that\u000aexplicitly use this filter with a BIO chain that can short-write and that\u000awrite large, newline-free data influenced by an attacker would be affected.\u000aHowever, the circumstances where this could happen are unlikely to be under\u000aattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\u000adata controlled by an attacker. For that reason the issue was assessed as\u000aLow severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the BIO implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-68160\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)",
      "type" : "CVE-2025-68160"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-bf33b39c",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68160: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68160**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)|\u000a\u000aIssue summary: Writing large, newline-free data into a BIO chain using the\u000aline-buffering filter where the next BIO performs short writes can trigger\u000aa heap-based out-of-bounds write.\u000a\u000aImpact summary: This out-of-bounds write can cause memory corruption which\u000atypically results in a crash, leading to Denial of Service for an application.\u000a\u000aThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\u000aTLS/SSL data paths. In OpenSSL command-line applications, it is typically\u000aonly pushed onto stdout/stderr on VMS systems. Third-party applications that\u000aexplicitly use this filter with a BIO chain that can short-write and that\u000awrite large, newline-free data influenced by an attacker would be affected.\u000aHowever, the circumstances where this could happen are unlikely to be under\u000aattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\u000adata controlled by an attacker. For that reason the issue was assessed as\u000aLow severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the BIO implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-68160\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-68160: : CVE-2025-68160: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to out-of-bounds write in BIO filter\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68160**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)|\u000a\u000aIssue summary: Writing large, newline-free data into a BIO chain using the\u000aline-buffering filter where the next BIO performs short writes can trigger\u000aa heap-based out-of-bounds write.\u000a\u000aImpact summary: This out-of-bounds write can cause memory corruption which\u000atypically results in a crash, leading to Denial of Service for an application.\u000a\u000aThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\u000aTLS/SSL data paths. In OpenSSL command-line applications, it is typically\u000aonly pushed onto stdout/stderr on VMS systems. Third-party applications that\u000aexplicitly use this filter with a BIO chain that can short-write and that\u000awrite large, newline-free data influenced by an attacker would be affected.\u000aHowever, the circumstances where this could happen are unlikely to be under\u000aattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\u000adata controlled by an attacker. For that reason the issue was assessed as\u000aLow severity.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the BIO implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-68160\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-68160](https://avd.aquasec.com/nvd/cve-2025-68160)",
      "type" : "CVE-2025-68160"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f0c038bb",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69418: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB encryption/decryption calls\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69418**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)|\u000a\u000aIssue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69418\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69418: : CVE-2025-69418: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB encryption/decryption calls\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69418**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)|\u000a\u000aIssue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69418\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)",
      "type" : "CVE-2025-69418"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f0c038bb",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69418: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB encryption/decryption calls\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69418**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)|\u000a\u000aIssue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69418\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69418: : CVE-2025-69418: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Information disclosure and data tampering via specific low-level OCB encryption/decryption calls\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69418**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)|\u000a\u000aIssue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69418\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69418](https://avd.aquasec.com/nvd/cve-2025-69418)",
      "type" : "CVE-2025-69418"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-cee93daf",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69419: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69419**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.5-r0|[CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)|\u000a\u000aIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously\u000acrafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing\u000anon-ASCII BMP code point can trigger a one byte write before the allocated\u000abuffer.\u000a\u000aImpact summary: The out-of-bounds write can cause a memory corruption\u000awhich can have various consequences including a Denial of Service.\u000a\u000aThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12\u000aBMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,\u000athe helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16\u000asource byte count as the destination buffer capacity to UTF8_putc(). For BMP\u000acode points above U+07FF, UTF-8 requires three bytes, but the forwarded\u000acapacity can be just two bytes. UTF8_putc() then returns -1, and this negative\u000avalue is added to the output length without validation, causing the\u000alength to become negative. The subsequent trailing NUL byte is then written\u000aat a negative offset, causing write outside of heap allocated buffer.\u000a\u000aThe vulnerability is reachable via the public PKCS12_get_friendlyname() API\u000awhen parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a\u000adifferent code path that avoids this issue, PKCS12_get_friendlyname() directly\u000ainvokes the vulnerable function. Exploitation requires an attacker to provide\u000aa malicious PKCS#12 file to be parsed by the application and the attacker\u000acan just trigger a one zero byte write before the allocated buffer.\u000aFor that reason the issue was assessed as Low severity according to our\u000aSecurity Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69419\u000aSeverity: HIGH\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2025-69419: : CVE-2025-69419: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69419**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.5-r0|[CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)|\u000a\u000aIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously\u000acrafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing\u000anon-ASCII BMP code point can trigger a one byte write before the allocated\u000abuffer.\u000a\u000aImpact summary: The out-of-bounds write can cause a memory corruption\u000awhich can have various consequences including a Denial of Service.\u000a\u000aThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12\u000aBMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,\u000athe helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16\u000asource byte count as the destination buffer capacity to UTF8_putc(). For BMP\u000acode points above U+07FF, UTF-8 requires three bytes, but the forwarded\u000acapacity can be just two bytes. UTF8_putc() then returns -1, and this negative\u000avalue is added to the output length without validation, causing the\u000alength to become negative. The subsequent trailing NUL byte is then written\u000aat a negative offset, causing write outside of heap allocated buffer.\u000a\u000aThe vulnerability is reachable via the public PKCS12_get_friendlyname() API\u000awhen parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a\u000adifferent code path that avoids this issue, PKCS12_get_friendlyname() directly\u000ainvokes the vulnerable function. Exploitation requires an attacker to provide\u000aa malicious PKCS#12 file to be parsed by the application and the attacker\u000acan just trigger a one zero byte write before the allocated buffer.\u000aFor that reason the issue was assessed as Low severity according to our\u000aSecurity Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69419\u000aSeverity: HIGH\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)",
      "type" : "CVE-2025-69419"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-cee93daf",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69419: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69419**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.5-r0|[CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)|\u000a\u000aIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously\u000acrafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing\u000anon-ASCII BMP code point can trigger a one byte write before the allocated\u000abuffer.\u000a\u000aImpact summary: The out-of-bounds write can cause a memory corruption\u000awhich can have various consequences including a Denial of Service.\u000a\u000aThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12\u000aBMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,\u000athe helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16\u000asource byte count as the destination buffer capacity to UTF8_putc(). For BMP\u000acode points above U+07FF, UTF-8 requires three bytes, but the forwarded\u000acapacity can be just two bytes. UTF8_putc() then returns -1, and this negative\u000avalue is added to the output length without validation, causing the\u000alength to become negative. The subsequent trailing NUL byte is then written\u000aat a negative offset, causing write outside of heap allocated buffer.\u000a\u000aThe vulnerability is reachable via the public PKCS12_get_friendlyname() API\u000awhen parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a\u000adifferent code path that avoids this issue, PKCS12_get_friendlyname() directly\u000ainvokes the vulnerable function. Exploitation requires an attacker to provide\u000aa malicious PKCS#12 file to be parsed by the application and the attacker\u000acan just trigger a one zero byte write before the allocated buffer.\u000aFor that reason the issue was assessed as Low severity according to our\u000aSecurity Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69419\u000aSeverity: HIGH\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2025-69419: : CVE-2025-69419: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69419**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libssl3|3.5.5-r0|[CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)|\u000a\u000aIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously\u000acrafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing\u000anon-ASCII BMP code point can trigger a one byte write before the allocated\u000abuffer.\u000a\u000aImpact summary: The out-of-bounds write can cause a memory corruption\u000awhich can have various consequences including a Denial of Service.\u000a\u000aThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12\u000aBMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes,\u000athe helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16\u000asource byte count as the destination buffer capacity to UTF8_putc(). For BMP\u000acode points above U+07FF, UTF-8 requires three bytes, but the forwarded\u000acapacity can be just two bytes. UTF8_putc() then returns -1, and this negative\u000avalue is added to the output length without validation, causing the\u000alength to become negative. The subsequent trailing NUL byte is then written\u000aat a negative offset, causing write outside of heap allocated buffer.\u000a\u000aThe vulnerability is reachable via the public PKCS12_get_friendlyname() API\u000awhen parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a\u000adifferent code path that avoids this issue, PKCS12_get_friendlyname() directly\u000ainvokes the vulnerable function. Exploitation requires an attacker to provide\u000aa malicious PKCS#12 file to be parsed by the application and the attacker\u000acan just trigger a one zero byte write before the allocated buffer.\u000aFor that reason the issue was assessed as Low severity according to our\u000aSecurity Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69419\u000aSeverity: HIGH\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69419](https://avd.aquasec.com/nvd/cve-2025-69419)",
      "type" : "CVE-2025-69419"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f351f662",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69420: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed TimeStamp Response\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69420**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the TimeStamp Response\u000averification code where an ASN1_TYPE union member is accessed without first\u000avalidating the type, causing an invalid or NULL pointer dereference when\u000aprocessing a malformed TimeStamp Response file.\u000a\u000aImpact summary: An application calling TS_RESP_verify_response() with a\u000amalformed TimeStamp Response can be caused to dereference an invalid or\u000aNULL pointer when reading, resulting in a Denial of Service.\u000a\u000aThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2()\u000aaccess the signing cert attribute value without validating its type.\u000aWhen the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory\u000athrough the ASN1_TYPE union, causing a crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000aTimeStamp Response to an application that verifies timestamp responses. The\u000aTimeStamp protocol (RFC 3161) is not widely used and the impact of the\u000aexploit is just a Denial of Service. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the TimeStamp Response implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69420\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69420: : CVE-2025-69420: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed TimeStamp Response\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69420**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the TimeStamp Response\u000averification code where an ASN1_TYPE union member is accessed without first\u000avalidating the type, causing an invalid or NULL pointer dereference when\u000aprocessing a malformed TimeStamp Response file.\u000a\u000aImpact summary: An application calling TS_RESP_verify_response() with a\u000amalformed TimeStamp Response can be caused to dereference an invalid or\u000aNULL pointer when reading, resulting in a Denial of Service.\u000a\u000aThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2()\u000aaccess the signing cert attribute value without validating its type.\u000aWhen the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory\u000athrough the ASN1_TYPE union, causing a crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000aTimeStamp Response to an application that verifies timestamp responses. The\u000aTimeStamp protocol (RFC 3161) is not widely used and the impact of the\u000aexploit is just a Denial of Service. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the TimeStamp Response implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69420\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)",
      "type" : "CVE-2025-69420"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f351f662",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69420: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed TimeStamp Response\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69420**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the TimeStamp Response\u000averification code where an ASN1_TYPE union member is accessed without first\u000avalidating the type, causing an invalid or NULL pointer dereference when\u000aprocessing a malformed TimeStamp Response file.\u000a\u000aImpact summary: An application calling TS_RESP_verify_response() with a\u000amalformed TimeStamp Response can be caused to dereference an invalid or\u000aNULL pointer when reading, resulting in a Denial of Service.\u000a\u000aThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2()\u000aaccess the signing cert attribute value without validating its type.\u000aWhen the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory\u000athrough the ASN1_TYPE union, causing a crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000aTimeStamp Response to an application that verifies timestamp responses. The\u000aTimeStamp protocol (RFC 3161) is not widely used and the impact of the\u000aexploit is just a Denial of Service. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the TimeStamp Response implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69420\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69420: : CVE-2025-69420: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed TimeStamp Response\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69420**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the TimeStamp Response\u000averification code where an ASN1_TYPE union member is accessed without first\u000avalidating the type, causing an invalid or NULL pointer dereference when\u000aprocessing a malformed TimeStamp Response file.\u000a\u000aImpact summary: An application calling TS_RESP_verify_response() with a\u000amalformed TimeStamp Response can be caused to dereference an invalid or\u000aNULL pointer when reading, resulting in a Denial of Service.\u000a\u000aThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2()\u000aaccess the signing cert attribute value without validating its type.\u000aWhen the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory\u000athrough the ASN1_TYPE union, causing a crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000aTimeStamp Response to an application that verifies timestamp responses. The\u000aTimeStamp protocol (RFC 3161) is not widely used and the impact of the\u000aexploit is just a Denial of Service. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the TimeStamp Response implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69420\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69420](https://avd.aquasec.com/nvd/cve-2025-69420)",
      "type" : "CVE-2025-69420"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f36e8f53",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69421: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69421**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)|\u000a\u000aIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\u000adereference in the PKCS12_item_decrypt_d2i_ex() function.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which leads to\u000aDenial of Service for an application processing PKCS#12 files.\u000a\u000aThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\u000aparameter is NULL before dereferencing it. When called from\u000aPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\u000abe NULL, causing a crash. The vulnerability is limited to Denial of Service\u000aand cannot be escalated to achieve code execution or memory disclosure.\u000a\u000aExploiting this issue requires an attacker to provide a malformed PKCS#12 file\u000ato an application that processes it. For that reason the issue was assessed as\u000aLow severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69421\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69421: : CVE-2025-69421: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69421**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)|\u000a\u000aIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\u000adereference in the PKCS12_item_decrypt_d2i_ex() function.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which leads to\u000aDenial of Service for an application processing PKCS#12 files.\u000a\u000aThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\u000aparameter is NULL before dereferencing it. When called from\u000aPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\u000abe NULL, causing a crash. The vulnerability is limited to Denial of Service\u000aand cannot be escalated to achieve code execution or memory disclosure.\u000a\u000aExploiting this issue requires an attacker to provide a malformed PKCS#12 file\u000ato an application that processes it. For that reason the issue was assessed as\u000aLow severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69421\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)",
      "type" : "CVE-2025-69421"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-f36e8f53",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-69421: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69421**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)|\u000a\u000aIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\u000adereference in the PKCS12_item_decrypt_d2i_ex() function.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which leads to\u000aDenial of Service for an application processing PKCS#12 files.\u000a\u000aThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\u000aparameter is NULL before dereferencing it. When called from\u000aPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\u000abe NULL, causing a crash. The vulnerability is limited to Denial of Service\u000aand cannot be escalated to achieve code execution or memory disclosure.\u000a\u000aExploiting this issue requires an attacker to provide a malformed PKCS#12 file\u000ato an application that processes it. For that reason the issue was assessed as\u000aLow severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69421\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2025-69421: : CVE-2025-69421: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via malformed PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2025-69421**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)|\u000a\u000aIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\u000adereference in the PKCS12_item_decrypt_d2i_ex() function.\u000a\u000aImpact summary: A NULL pointer dereference can trigger a crash which leads to\u000aDenial of Service for an application processing PKCS#12 files.\u000a\u000aThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\u000aparameter is NULL before dereferencing it. When called from\u000aPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\u000abe NULL, causing a crash. The vulnerability is limited to Denial of Service\u000aand cannot be escalated to achieve code execution or memory disclosure.\u000a\u000aExploiting this issue requires an attacker to provide a malformed PKCS#12 file\u000ato an application that processes it. For that reason the issue was assessed as\u000aLow severity according to our Security Policy.\u000a\u000aThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2025-69421\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2025-69421](https://avd.aquasec.com/nvd/cve-2025-69421)",
      "type" : "CVE-2025-69421"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-c72f0d29",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22695: OsPackageVulnerability\u000a\u000alibpng: libpng: Denial of service and information disclosure via heap buffer over-read in png_image_finish_read\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22695**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libpng|1.6.54-r0|[CVE-2026-22695](https://avd.aquasec.com/nvd/cve-2026-22695)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.53-r0\u000aVulnerability CVE-2026-22695\u000aSeverity: HIGH\u000aFixed Version: 1.6.54-r0\u000aLink: [CVE-2026-22695](https://avd.aquasec.com/nvd/cve-2026-22695)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2026-22695: : CVE-2026-22695: OsPackageVulnerability\u000a\u000alibpng: libpng: Denial of service and information disclosure via heap buffer over-read in png_image_finish_read\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22695**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libpng|1.6.54-r0|[CVE-2026-22695](https://avd.aquasec.com/nvd/cve-2026-22695)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.53-r0\u000aVulnerability CVE-2026-22695\u000aSeverity: HIGH\u000aFixed Version: 1.6.54-r0\u000aLink: [CVE-2026-22695](https://avd.aquasec.com/nvd/cve-2026-22695)",
      "type" : "CVE-2026-22695"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-547cc1d7",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22795: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22795**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)|\u000a\u000aIssue summary: An invalid or NULL pointer dereference can happen in\u000aan application processing a malformed PKCS#12 file.\u000a\u000aImpact summary: An application processing a malformed PKCS#12 file can be\u000acaused to dereference an invalid or NULL pointer on memory read, resulting\u000ain a Denial of Service.\u000a\u000aA type confusion vulnerability exists in PKCS#12 parsing code where\u000aan ASN1_TYPE union member is accessed without first validating the type,\u000acausing an invalid pointer read.\u000a\u000aThe location is constrained to a 1-byte address space, meaning any\u000aattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u000aThis range corresponds to the zero page, which is unmapped on most modern\u000aoperating systems and will reliably result in a crash, leading only to a\u000aDenial of Service. Exploiting this issue also requires a user or application\u000ato process a maliciously crafted PKCS#12 file. It is uncommon to accept\u000auntrusted PKCS#12 files in applications as they are usually used to store\u000aprivate keys which are trusted by definition. For these reasons, the issue\u000awas assessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22795\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2026-22795: : CVE-2026-22795: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22795**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)|\u000a\u000aIssue summary: An invalid or NULL pointer dereference can happen in\u000aan application processing a malformed PKCS#12 file.\u000a\u000aImpact summary: An application processing a malformed PKCS#12 file can be\u000acaused to dereference an invalid or NULL pointer on memory read, resulting\u000ain a Denial of Service.\u000a\u000aA type confusion vulnerability exists in PKCS#12 parsing code where\u000aan ASN1_TYPE union member is accessed without first validating the type,\u000acausing an invalid pointer read.\u000a\u000aThe location is constrained to a 1-byte address space, meaning any\u000aattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u000aThis range corresponds to the zero page, which is unmapped on most modern\u000aoperating systems and will reliably result in a crash, leading only to a\u000aDenial of Service. Exploiting this issue also requires a user or application\u000ato process a maliciously crafted PKCS#12 file. It is uncommon to accept\u000auntrusted PKCS#12 files in applications as they are usually used to store\u000aprivate keys which are trusted by definition. For these reasons, the issue\u000awas assessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22795\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)",
      "type" : "CVE-2026-22795"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-547cc1d7",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22795: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22795**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)|\u000a\u000aIssue summary: An invalid or NULL pointer dereference can happen in\u000aan application processing a malformed PKCS#12 file.\u000a\u000aImpact summary: An application processing a malformed PKCS#12 file can be\u000acaused to dereference an invalid or NULL pointer on memory read, resulting\u000ain a Denial of Service.\u000a\u000aA type confusion vulnerability exists in PKCS#12 parsing code where\u000aan ASN1_TYPE union member is accessed without first validating the type,\u000acausing an invalid pointer read.\u000a\u000aThe location is constrained to a 1-byte address space, meaning any\u000aattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u000aThis range corresponds to the zero page, which is unmapped on most modern\u000aoperating systems and will reliably result in a crash, leading only to a\u000aDenial of Service. Exploiting this issue also requires a user or application\u000ato process a maliciously crafted PKCS#12 file. It is uncommon to accept\u000auntrusted PKCS#12 files in applications as they are usually used to store\u000aprivate keys which are trusted by definition. For these reasons, the issue\u000awas assessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22795\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2026-22795: : CVE-2026-22795: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22795**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)|\u000a\u000aIssue summary: An invalid or NULL pointer dereference can happen in\u000aan application processing a malformed PKCS#12 file.\u000a\u000aImpact summary: An application processing a malformed PKCS#12 file can be\u000acaused to dereference an invalid or NULL pointer on memory read, resulting\u000ain a Denial of Service.\u000a\u000aA type confusion vulnerability exists in PKCS#12 parsing code where\u000aan ASN1_TYPE union member is accessed without first validating the type,\u000acausing an invalid pointer read.\u000a\u000aThe location is constrained to a 1-byte address space, meaning any\u000aattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u000aThis range corresponds to the zero page, which is unmapped on most modern\u000aoperating systems and will reliably result in a crash, leading only to a\u000aDenial of Service. Exploiting this issue also requires a user or application\u000ato process a maliciously crafted PKCS#12 file. It is uncommon to accept\u000auntrusted PKCS#12 files in applications as they are usually used to store\u000aprivate keys which are trusted by definition. For these reasons, the issue\u000awas assessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u000a\u000aOpenSSL 1.0.2 is not affected by this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22795\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22795](https://avd.aquasec.com/nvd/cve-2026-22795)",
      "type" : "CVE-2026-22795"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-54995ac8",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22796: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22796**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the signature\u000averification of signed PKCS#7 data where an ASN1_TYPE union member is\u000aaccessed without first validating the type, causing an invalid or NULL\u000apointer dereference when processing malformed PKCS#7 data.\u000a\u000aImpact summary: An application performing signature verification of PKCS#7\u000adata or calling directly the PKCS7_digest_from_attributes() function can be\u000acaused to dereference an invalid or NULL pointer when reading, resulting in\u000aa Denial of Service.\u000a\u000aThe function PKCS7_digest_from_attributes() accesses the message digest attribute\u000avalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\u000athis results in accessing invalid memory through the ASN1_TYPE union, causing\u000aa crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000asigned PKCS#7 to an application that verifies it. The impact of the\u000aexploit is just a Denial of Service, the PKCS7 API is legacy and applications\u000ashould be using the CMS API instead. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22796\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2026-22796: : CVE-2026-22796: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22796**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the signature\u000averification of signed PKCS#7 data where an ASN1_TYPE union member is\u000aaccessed without first validating the type, causing an invalid or NULL\u000apointer dereference when processing malformed PKCS#7 data.\u000a\u000aImpact summary: An application performing signature verification of PKCS#7\u000adata or calling directly the PKCS7_digest_from_attributes() function can be\u000acaused to dereference an invalid or NULL pointer when reading, resulting in\u000aa Denial of Service.\u000a\u000aThe function PKCS7_digest_from_attributes() accesses the message digest attribute\u000avalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\u000athis results in accessing invalid memory through the ASN1_TYPE union, causing\u000aa crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000asigned PKCS#7 to an application that verifies it. The impact of the\u000aexploit is just a Denial of Service, the PKCS7 API is legacy and applications\u000ashould be using the CMS API instead. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libcrypto3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22796\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)",
      "type" : "CVE-2026-22796"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-54995ac8",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22796: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22796**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the signature\u000averification of signed PKCS#7 data where an ASN1_TYPE union member is\u000aaccessed without first validating the type, causing an invalid or NULL\u000apointer dereference when processing malformed PKCS#7 data.\u000a\u000aImpact summary: An application performing signature verification of PKCS#7\u000adata or calling directly the PKCS7_digest_from_attributes() function can be\u000acaused to dereference an invalid or NULL pointer when reading, resulting in\u000aa Denial of Service.\u000a\u000aThe function PKCS7_digest_from_attributes() accesses the message digest attribute\u000avalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\u000athis results in accessing invalid memory through the ASN1_TYPE union, causing\u000aa crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000asigned PKCS#7 to an application that verifies it. The impact of the\u000aexploit is just a Denial of Service, the PKCS7 API is legacy and applications\u000ashould be using the CMS API instead. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22796\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "govway(1,0): CVE-2026-22796: : CVE-2026-22796: OsPackageVulnerability\u000a\u000aopenssl: OpenSSL: Denial of Service via type confusion in PKCS#7 signature verification\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22796**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|libssl3|3.5.5-r0|[CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)|\u000a\u000aIssue summary: A type confusion vulnerability exists in the signature\u000averification of signed PKCS#7 data where an ASN1_TYPE union member is\u000aaccessed without first validating the type, causing an invalid or NULL\u000apointer dereference when processing malformed PKCS#7 data.\u000a\u000aImpact summary: An application performing signature verification of PKCS#7\u000adata or calling directly the PKCS7_digest_from_attributes() function can be\u000acaused to dereference an invalid or NULL pointer when reading, resulting in\u000aa Denial of Service.\u000a\u000aThe function PKCS7_digest_from_attributes() accesses the message digest attribute\u000avalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\u000athis results in accessing invalid memory through the ASN1_TYPE union, causing\u000aa crash.\u000a\u000aExploiting this vulnerability requires an attacker to provide a malformed\u000asigned PKCS#7 to an application that verifies it. The impact of the\u000aexploit is just a Denial of Service, the PKCS7 API is legacy and applications\u000ashould be using the CMS API instead. For these reasons the issue was\u000aassessed as Low severity.\u000a\u000aThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u000aas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\u000aboundary.\u000a\u000aOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.\u000a\u000aPackage: libssl3\u000aInstalled Version: 3.5.4-r0\u000aVulnerability CVE-2026-22796\u000aSeverity: MEDIUM\u000aFixed Version: 3.5.5-r0\u000aLink: [CVE-2026-22796](https://avd.aquasec.com/nvd/cve-2026-22796)",
      "type" : "CVE-2026-22796"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "govway",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/linkitaly/govway",
      "fingerprint" : "FALLBACK-7e463c20",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-22801: OsPackageVulnerability\u000a\u000alibpng: libpng: Information disclosure and denial of service via integer truncation in simplified write API\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22801**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libpng|1.6.54-r0|[CVE-2026-22801](https://avd.aquasec.com/nvd/cve-2026-22801)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.53-r0\u000aVulnerability CVE-2026-22801\u000aSeverity: HIGH\u000aFixed Version: 1.6.54-r0\u000aLink: [CVE-2026-22801](https://avd.aquasec.com/nvd/cve-2026-22801)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "govway(1,0): CVE-2026-22801: : CVE-2026-22801: OsPackageVulnerability\u000a\u000alibpng: libpng: Information disclosure and denial of service via integer truncation in simplified write API\u000a\u000aFor additional help see: **Vulnerability CVE-2026-22801**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|libpng|1.6.54-r0|[CVE-2026-22801](https://avd.aquasec.com/nvd/cve-2026-22801)|\u000a\u000aLIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.\u000a\u000aPackage: libpng\u000aInstalled Version: 1.6.53-r0\u000aVulnerability CVE-2026-22801\u000aSeverity: HIGH\u000aFixed Version: 1.6.54-r0\u000aLink: [CVE-2026-22801](https://avd.aquasec.com/nvd/cve-2026-22801)",
      "type" : "CVE-2026-22801"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/var/govway/batch/generatoreStatistiche/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/var/govway/batch/generatoreStatistiche/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govway.war/WEB-INF/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "struts-core-1.3.10.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/struts-core-1.3.10.jar",
      "fingerprint" : "FALLBACK-19072676",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "type" : "CVE-2023-34396"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "jasperreports-6.20.0.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jar",
      "fingerprint" : "FALLBACK-b0f36103",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports||[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "jasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports||[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)",
      "type" : "CVE-2025-10492"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIMonitor.war/WEB-INF/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "struts-core-1.3.10.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayConsole.war/WEB-INF/lib/struts-core-1.3.10.jar",
      "fingerprint" : "FALLBACK-19072676",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "type" : "CVE-2023-34396"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "commons-lang-2.6.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/commons-lang-2.6.jar",
      "fingerprint" : "FALLBACK-f48ad3a6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "commons-lang-2.6.jar(1,0): CVE-2025-48924: : CVE-2025-48924: LanguageSpecificPackageVulnerability\u000a\u000acommons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang\u000a\u000aFor additional help see: **Vulnerability CVE-2025-48924**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|commons-lang:commons-lang||[CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)|\u000a\u000aUncontrolled Recursion vulnerability in Apache Commons Lang.\u000a\u000aThis issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0.\u000a\u000aThe methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a \u000aStackOverflowError could cause an application to stop.\u000a\u000aUsers are recommended to upgrade to version 3.18.0, which fixes the issue.\u000a\u000aPackage: commons-lang:commons-lang\u000aInstalled Version: 2.6\u000aVulnerability CVE-2025-48924\u000aSeverity: MEDIUM\u000aFixed Version: \u000aLink: [CVE-2025-48924](https://avd.aquasec.com/nvd/cve-2025-48924)",
      "type" : "CVE-2025-48924"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "jasperreports-6.20.0.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/jasperreports-6.20.0.jar",
      "fingerprint" : "FALLBACK-b0f36103",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports||[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "jasperreports-6.20.0.jar(1,0): CVE-2025-10492: : CVE-2025-10492: LanguageSpecificPackageVulnerability\u000a\u000aJasperReports has a Java deserialisation vulnerability\u000a\u000aFor additional help see: **Vulnerability CVE-2025-10492**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|net.sf.jasperreports:jasperreports||[CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)|\u000a\u000aA Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library\u000a\u000aPackage: net.sf.jasperreports:jasperreports\u000aInstalled Version: 6.20.0\u000aVulnerability CVE-2025-10492\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2025-10492](https://avd.aquasec.com/nvd/cve-2025-10492)",
      "type" : "CVE-2025-10492"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.24.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-core-2.24.3.jar",
      "fingerprint" : "FALLBACK-d199ac3f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.24.3.jar(1,0): CVE-2025-68161: : CVE-2025-68161: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j: Apache Log4j Core: Information disclosure via missing TLS hostname verification\u000a\u000aFor additional help see: **Vulnerability CVE-2025-68161**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.3|[CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)|\u000a\u000aThe Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not perform TLS hostname verification of the peer certificate, even when the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  configuration attribute or the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property is set to true.\u000a\u000aThis issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions:\u000a\u000a  *  The attacker is able to intercept or redirect network traffic between the client and the log receiver.\u000a  *  The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured).\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue.\u000a\u000aAs an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.24.3\u000aVulnerability CVE-2025-68161\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.3\u000aLink: [CVE-2025-68161](https://avd.aquasec.com/nvd/cve-2025-68161)",
      "type" : "CVE-2025-68161"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "struts-core-1.3.10.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/struts-core-1.3.10.jar",
      "fingerprint" : "FALLBACK-19072676",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1359",
      "severity" : "HIGH",
      "toString" : "struts-core-1.3.10.jar(1,0): CVE-2023-34396: : CVE-2023-34396: LanguageSpecificPackageVulnerability\u000a\u000aApache Struts vulnerable to memory exhaustion\u000a\u000aFor additional help see: **Vulnerability CVE-2023-34396**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|HIGH|org.apache.struts:struts-core||[CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)|\u000a\u000aAllocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.\u000a\u000aUpgrade to Struts 2.5.31 or 6.1.2.1 or greater\u000a\u000aPackage: org.apache.struts:struts-core\u000aInstalled Version: 1.3.10\u000aVulnerability CVE-2023-34396\u000aSeverity: HIGH\u000aFixed Version: \u000aLink: [CVE-2023-34396](https://avd.aquasec.com/nvd/cve-2023-34396)",
      "type" : "CVE-2023-34396"
    }
  ],
  "size" : 44,
  "toString" : "44 warnings (high: 11, normal: 33)"
}