8000 deps: upgrade openssl sources to quictls/openssl-3.0.12+quic1 · nodejs/node@a64217c · GitHub
[go: up one dir, main page]
Skip to content

Commit a64217c

Browse files
nodejs-github-bottargos
nodejs-github-bot
authored and
targos
committed
deps: upgrade openssl sources to quictls/openssl-3.0.12+quic1
PR-URL: #50411 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
1 parent d94010b commit a64217c

File tree

207 files changed

+1972
-797
lines changed
  • configuration.h
  • crmf.h
  • crypto.h
  • ct.h
  • err.h
  • ess.h
  • evp.h
  • fipskey.h
  • lhash.h
  • ocsp.h
  • opensslv.h
  • pkcs12.h
  • pkcs7.h.in
  • pkcs7.h
  • safestack.h
  • srp.h
  • ssl.h
  • ui.h
  • x509.h
  • x509_vfy.h
  • x509v3.h
  • providers
  • ssl
  • test
  • util

    • Some content is hidden

    Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

    207 files changed

    +1972
    -797
    lines changed

    ‎deps/openssl/openssl/CHANGES.md‎

    Lines changed: 35 additions & 1 deletion
    Original file line numberDiff line numberDiff line change
    @@ -28,12 +28,44 @@ breaking changes, and mappings for the large list of deprecated functions.
    2828

    2929
    [Migration guide]: https://github.com/openssl/openssl/tree/master/doc/man7/migration_guide.pod
    3030

    31-
    ### Changes between 3.0.10 and 3.0.10+quic [1 Aug 2023]
    31+
    ### Changes between 3.0.12 and 3.0.12+quic [24 Oct 2023]
    3232

    3333
    * Add QUIC API support from BoringSSL
    3434

    3535
    *Todd Short*
    3636

    37+
    ### Changes between 3.0.11 and 3.0.12 [24 Oct 2023]
    38+
    39+
    * Fix incorrect key and IV resizing issues when calling EVP_EncryptInit_ex2(),
    40+
    EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() with OSSL_PARAM parameters
    41+
    that alter the key or IV length ([CVE-2023-5363]).
    42+
    43+
    *Paul Dale*
    44+
    45+
    ### Changes between 3.0.10 and 3.0.11 [19 Sep 2023]
    46+
    47+
    * Fix POLY1305 MAC implementation corrupting XMM registers on Windows.
    48+
    49+
    The POLY1305 MAC (message authentication code) implementation in OpenSSL
    50+
    does not save the contents of non-volatile XMM registers on Windows 64
    51+
    platform when calculating the MAC of data larger than 64 bytes. Before
    52+
    returning to the caller all the XMM registers are set to zero rather than
    53+
    restoring their previous content. The vulnerable code is used only on newer
    54+
    x86_64 processors supporting the AVX512-IFMA instructions.
    55+
    56+
    The consequences of this kind of internal application state corruption can
    57+
    be various - from no consequences, if the calling application does not
    58+
    depend on the contents of non-volatile XMM registers at all, to the worst
    59+
    consequences, where the attacker could get complete control of the
    60+
    application process. However given the contents of the registers are just
    61+
    zeroized so the attacker cannot put arbitrary values inside, the most likely
    62+
    consequence, if any, would be an incorrect result of some application
    63+
    dependent calculations or a crash leading to a denial of service.
    64+
    65+
    ([CVE-2023-4807])
    66+
    67+
    *Bernd Edlinger*
    68+
    3769
    ### Changes between 3.0.9 and 3.0.10 [1 Aug 2023]
    3870

    3971
    * Fix excessive time spent checking DH q parameter value.
    @@ -19714,6 +19746,8 @@ ndif
    1971419746

    1971519747
    <!-- Links -->
    1971619748

    19749+
    [CVE-2023-5363]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-5363
    19750+
    [CVE-2023-4807]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-4807
    1971719751
    [CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817
    1971819752
    [CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446
    1971919753
    [CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975

    ‎deps/openssl/openssl/Configurations/10-main.conf‎

    Lines changed: 7 additions & 4 deletions
    Original file line numberDiff line numberDiff line change
    @@ -9,19 +9,22 @@ sub vc_win64a_info {
    99
    $vc_win64a_info = { AS => "nasm",
    1010
    ASFLAGS => "-g",
    1111
    asflags => "-Ox -f win64 -DNEAR",
    12-
    asoutflag => "-o " };
    12+
    asoutflag => "-o ",
    13+
    perlasm_scheme => "nasm" };
    1314
    } elsif ($disabled{asm}) {
    1415
    # assembler is still used to compile uplink shim
    1516
    $vc_win64a_info = { AS => "ml64",
    1617
    ASFLAGS => "/nologo /Zi",
    1718
    asflags => "/c /Cp /Cx",
    18-
    asoutflag => "/Fo" };
    19+
    asoutflag => "/Fo",
    20+
    perlasm_scheme => "masm" };
    1921
    } else {
    2022
    $die->("NASM not found - make sure it's installed and available on %PATH%\n");
    2123
    $vc_win64a_info = { AS => "{unknown}",
    2224
    ASFLAGS => "",
    2325
    asflags => "",
    24-
    asoutflag => "" };
    26+
    asoutflag => "",
    27+
    perlasm_scheme => "auto" };
    25< 77D code>28
    }
    2629
    }
    2730
    return $vc_win64a_info;
    @@ -1416,7 +1419,7 @@ my %targets = (
    14161419
    sys_id => "WIN64A",
    14171420
    uplink_arch => 'x86_64',
    14181421
    asm_arch => 'x86_64',
    1419-
    perlasm_scheme => "auto",
    1422+
    perlasm_scheme => sub { vc_win64a_info()->{perlasm_scheme} },
    14201423
    multilib => "-x64",
    14211424
    },
    14221425
    "VC-WIN32" => {

    ‎deps/openssl/openssl/Configurations/README.md‎

    Lines changed: 6 additions & 0 deletions
    Original file line numberDiff line numberDiff line change
    @@ -233,8 +233,14 @@ In each table entry, the following keys are significant:
    233233
    is ILP32;
    234234
    RC4_CHAR RC4 key schedule is made
    235235
    up of 'unsigned char's;
    236+
    Note: should not be used
    237+
    for new configuration
    238+
    targets
    236239
    RC4_INT RC4 key schedule is made
    237240
    up of 'unsigned int's;
    241+
    Note: should not be used
    242+
    for new configuration
    243+
    targets
    238244

    239245
    [1] as part of the target configuration, one can have a key called
    240246
    `inherit_from` that indicates what other configurations to inherit

    0 commit comments

    Comments
     (0)
    0