OPENSUSE-SU-2026:20473-1

Vulnerability from csaf_opensuse - Published: 2026-04-07 07:50 - Updated: 2026-04-07 07:50
Summary
Security update for osslsigncode
Severity
Critical
Notes
Title of the patch: Security update for osslsigncode
Description of the patch: This update for osslsigncode fixes the following issues: Changes in osslsigncode: - Update to 2.13 (bsc#1260680, CVE-2025-70888): * fixed integer overflows when processing APPX compressed data streams * fixed double-free vulnerabilities in APPX file processing * fixed multiple memory corruption issues in PE page hash computation - Changes from 2.12: * fixed a buffer overflow while extracting message digests - Changes from 2.11: * added keyUsage validation for signer certificate * added printing CRL details during signature verification * implemented a workaround for CRL servers returning the HTTP Content-Type header other than application/pkix-crl * fixed HTTP keep-alive handling * fixed macOS compiler and linker flags * fixed undefined BIO_get_fp() behavior with BIO_FLAGS_UPLINK_INTERNAL - update to 2.10: * added JavaScript signing * added PKCS#11 provider support (requires OpenSSL 3.0+) * added support for providers without specifying "-pkcs11module" option * (OpenSSL 3.0+, e.g., for the upcoming CNG provider) * added compatibility with the CNG engine version 1.1 or later * added the "-engineCtrl" option to control hardware and CNG engines * added the '-blobFile' option to specify a file containing the blob content * improved unauthenticated blob support (thanks to Asger Hautop Drewsen) * improved UTF-8 handling for certificate subjects and issuers * fixed support for multiple signerInfo contentType OIDs (CTL and Authenticode) * fixed tests for python-cryptography >= 43.0.0 - update to version 2.9: * added a 64 bit long pseudo-random NONCE in the TSA request * missing NID_pkcs9_signingTime is no longer an error * added support for PEM-encoded CRLs * fixed the APPX central directory sorting order * added a special "-" file name to read the passphrase from stdin * used native HTTP client with OpenSSL 3.x, removing libcurl dependency * added '-login' option to force a login to PKCS11 engines * added the "-ignore-crl" option to disable fetching and verifying CRL Distribution Points * changed error output to stderr instead of stdout * various testing framework improvements * various memory corruption fixes - update to version 2.8: * Microsoft PowerShell signing sponsored by Cisco Systems, Inc. * fixed setting unauthenticated attributes (Countersignature, Unauthenticated * Data Blob) in a nested signature * added the "-index" option to verify a specific signature or modify its unauthenticated attributes * added CAT file verification * added listing the contents of a CAT file with the "-verbose" option * added the new "extract-data" command to extract a PKCS#7 data content to be signed with "sign" and attached with "attach-signature" * added PKCS9_SEQUENCE_NUMBER authenticated attribute support * added the "-ignore-cdp" option to disable CRL Distribution Points (CDP) online verification * unsuccessful CRL retrieval and verification changed into a critical error the "-p" option modified to also use to configured proxy to connect CRL Distribution Points * added implicit allowlisting of the Microsoft Root Authority serial number 00C1008B3C3C8811D13EF663ECDF40 * added listing of certificate chain retrieved from the signature in case of verification failure
Patchnames: openSUSE-Leap-16.0-packagehub-187
Terms of use: CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
Vendor Fix To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

{
  "document": {
    "aggregate_severity": {
      "namespace": "https://www.suse.com/support/security/rating/",
      "text": "critical"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "Copyright 2024 SUSE LLC. All rights reserved.",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "Security update for osslsigncode",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "This update for osslsigncode fixes the following issues:\n\nChanges in osslsigncode:\n\n- Update to 2.13 (bsc#1260680, CVE-2025-70888):\n  * fixed integer overflows when processing APPX compressed data\n    streams\n  * fixed double-free vulnerabilities in APPX file processing\n  * fixed multiple memory corruption issues in PE page hash\n    computation\n\n- Changes from 2.12:\n  * fixed a buffer overflow while extracting message digests\n\n- Changes from 2.11:\n  * added keyUsage validation for signer certificate\n  * added printing CRL details during signature verification\n  * implemented a workaround for CRL servers returning the\n    HTTP Content-Type header other than application/pkix-crl\n  * fixed HTTP keep-alive handling\n  * fixed macOS compiler and linker flags\n  * fixed undefined BIO_get_fp() behavior with\n    BIO_FLAGS_UPLINK_INTERNAL\n\n- update to 2.10:\n  * added JavaScript signing\n  * added PKCS#11 provider support (requires OpenSSL 3.0+)\n  * added support for providers without specifying\n    \"-pkcs11module\" option\n  * (OpenSSL 3.0+, e.g., for the upcoming CNG provider)\n  * added compatibility with the CNG engine version 1.1 or later\n  * added the \"-engineCtrl\" option to control hardware and CNG\n    engines\n  * added the \u0027-blobFile\u0027 option to specify a file containing the\n    blob content\n  * improved unauthenticated blob support (thanks to Asger Hautop\n    Drewsen)\n  * improved UTF-8 handling for certificate subjects and issuers\n  * fixed support for multiple signerInfo contentType OIDs (CTL\n    and Authenticode)\n  * fixed tests for python-cryptography \u003e= 43.0.0\n\n- update to version 2.9:\n  * added a 64 bit long pseudo-random NONCE in the TSA request\n  * missing NID_pkcs9_signingTime is no longer an error\n  * added support for PEM-encoded CRLs\n  * fixed the APPX central directory sorting order\n  * added a special \"-\" file name to read the passphrase from\n    stdin\n  * used native HTTP client with OpenSSL 3.x, removing libcurl\n    dependency\n  * added \u0027-login\u0027 option to force a login to PKCS11 engines\n  * added the \"-ignore-crl\" option to disable fetching and\n    verifying CRL Distribution Points\n  * changed error output to stderr instead of stdout\n  * various testing framework improvements\n  * various memory corruption fixes\n\n- update to version 2.8:\n  * Microsoft PowerShell signing sponsored by Cisco Systems, Inc.\n  * fixed setting unauthenticated attributes (Countersignature,\n    Unauthenticated\n  * Data Blob) in a nested signature\n  * added the \"-index\" option to verify a specific signature or\n    modify its unauthenticated attributes\n  * added CAT file verification\n  * added listing the contents of a CAT file with the \"-verbose\"\n    option\n  * added the new \"extract-data\" command to extract a PKCS#7 data\n    content to be signed with \"sign\" and attached with \"attach-signature\"\n  * added PKCS9_SEQUENCE_NUMBER authenticated attribute support\n  * added the \"-ignore-cdp\" option to disable CRL Distribution\n    Points (CDP) online verification\n  * unsuccessful CRL retrieval and verification changed into a\n    critical error the \"-p\" option modified to also use to\n    configured proxy to connect CRL Distribution Points\n  * added implicit allowlisting of the Microsoft Root Authority\n    serial number 00C1008B3C3C8811D13EF663ECDF40\n  * added listing of certificate chain retrieved from the\n    signature in case of verification failure\n",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "openSUSE-Leap-16.0-packagehub-187",
        "title": "Patchnames"
      },
      {
        "category": "legal_disclaimer",
        "text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
        "title": "Terms of use"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://www.suse.com/support/security/contact/",
      "name": "SUSE Product Security Team",
      "namespace": "https://www.suse.com/"
    },
    "references": [
      {
        "category": "external",
        "summary": "SUSE ratings",
        "url": "https://www.suse.com/support/security/rating/"
      },
      {
        "category": "self",
        "summary": "URL of this CSAF notice",
        "url": "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_20473-1.json"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1260680",
        "url": "https://bugzilla.suse.com/1260680"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2025-70888 page",
        "url": "https://www.suse.com/security/cve/CVE-2025-70888/"
      }
    ],
    "title": "Security update for osslsigncode",
    "tracking": {
      "current_release_date": "2026-04-07T07:50:40Z",
      "generator": {
        "date": "2026-04-07T07:50:40Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "openSUSE-SU-2026:20473-1",
      "initial_release_date": "2026-04-07T07:50:40Z",
      "revision_history": [
        {
          "date": "2026-04-07T07:50:40Z",
          "number": "1",
          "summary": "Current version"
        }
      ],
      "status": "final",
      "version": "1"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "osslsigncode-2.13-bp160.1.1.aarch64",
                "product": {
                  "name": "osslsigncode-2.13-bp160.1.1.aarch64",
                  "product_id": "osslsigncode-2.13-bp160.1.1.aarch64"
                }
              }
            ],
            "category": "architecture",
            "name": "aarch64"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "osslsigncode-2.13-bp160.1.1.ppc64le",
                "product": {
                  "name": "osslsigncode-2.13-bp160.1.1.ppc64le",
                  "product_id": "osslsigncode-2.13-bp160.1.1.ppc64le"
                }
              }
            ],
            "category": "architecture",
            "name": "ppc64le"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "osslsigncode-2.13-bp160.1.1.s390x",
                "product": {
                  "name": "osslsigncode-2.13-bp160.1.1.s390x",
                  "product_id": "osslsigncode-2.13-bp160.1.1.s390x"
                }
              }
            ],
            "category": "architecture",
            "name": "s390x"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "osslsigncode-2.13-bp160.1.1.x86_64",
                "product": {
                  "name": "osslsigncode-2.13-bp160.1.1.x86_64",
                  "product_id": "osslsigncode-2.13-bp160.1.1.x86_64"
                }
              }
            ],
            "category": "architecture",
            "name": "x86_64"
          },
          {
            "branches": [
              {
                "category": "product_name",
                "name": "openSUSE Leap 16.0",
                "product": {
                  "name": "openSUSE Leap 16.0",
                  "product_id": "openSUSE Leap 16.0"
                }
              }
            ],
            "category": "product_family",
            "name": "SUSE Linux Enterprise"
          }
        ],
        "category": "vendor",
        "name": "SUSE"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "osslsigncode-2.13-bp160.1.1.aarch64 as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.aarch64"
        },
        "product_reference": "osslsigncode-2.13-bp160.1.1.aarch64",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "osslsigncode-2.13-bp160.1.1.ppc64le as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.ppc64le"
        },
        "product_reference": "osslsigncode-2.13-bp160.1.1.ppc64le",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "osslsigncode-2.13-bp160.1.1.s390x as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.s390x"
        },
        "product_reference": "osslsigncode-2.13-bp160.1.1.s390x",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "osslsigncode-2.13-bp160.1.1.x86_64 as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.x86_64"
        },
        "product_reference": "osslsigncode-2.13-bp160.1.1.x86_64",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2025-70888",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2025-70888"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "An issue in mtrojnar Osslsigncode affected at v2.10 and before allows a remote attacker to escalate privileges via the osslsigncode.c component",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.aarch64",
          "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.ppc64le",
          "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.s390x",
          "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.x86_64"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2025-70888",
          "url": "https://www.suse.com/security/cve/CVE-2025-70888"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1260680 for CVE-2025-70888",
          "url": "https://bugzilla.suse.com/1260680"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
          "product_ids": [
            "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.aarch64",
            "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.ppc64le",
            "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.s390x",
            "openSUSE Leap 16.0:osslsigncode-2.13-bp160.1.1.x86_64"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2026-04-07T07:50:40Z",
          "details": "critical"
        }
      ],
      "title": "CVE-2025-70888"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…