Vulnerabilities

180 via 180 paths

Dependencies

103

Source

Group 6 Copy Created with Sketch. Docker

Target OS

amzn:2018.03
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 6
  • 59
  • 115
Status
  • 180
  • 0
  • 0

critical severity

Inappropriate Encoding for Output Context

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-12.27.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

xmltok_impl.c in Expat (aka libexpat) before 2.4.5 lacks certain validation of encoding, such as checks for whether a UTF-8 character is valid in a certain context.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-12.27.amzn1 or higher.
This issue was patched in ALAS-2022-1573.

References

critical severity

Incorrect Behavior Order: Early Validation

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-12.27.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

xmlparse.c in Expat (aka libexpat) before 2.4.5 allows attackers to insert namespace-separator characters into namespace URIs.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-12.27.amzn1 or higher.
This issue was patched in ALAS-2022-1573.

References

critical severity

Buffer Overflow

  • Vulnerable module: nss
  • Introduced through: nss@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.87.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures encoded within CMS, S/MIME, PKCS #7, or PKCS #12 are likely to be impacted. Applications using NSS for certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how they configure NSS. Note: This vulnerability does NOT impact Mozilla Firefox. However, email clients and PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1.

Remediation

Upgrade Amazon-Linux:2018.03 nss to version 0:3.53.1-7.87.amzn1 or higher.
This issue was patched in ALAS-2021-1552.

References

critical severity

Buffer Overflow

  • Vulnerable module: nss-sysinit
  • Introduced through: nss-sysinit@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.87.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-sysinit@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-sysinit package and not the nss-sysinit package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures encoded within CMS, S/MIME, PKCS #7, or PKCS #12 are likely to be impacted. Applications using NSS for certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how they configure NSS. Note: This vulnerability does NOT impact Mozilla Firefox. However, email clients and PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1.

Remediation

Upgrade Amazon-Linux:2018.03 nss-sysinit to version 0:3.53.1-7.87.amzn1 or higher.
This issue was patched in ALAS-2021-1552.

References

critical severity

Buffer Overflow

  • Vulnerable module: nss-tools
  • Introduced through: nss-tools@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.87.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-tools@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-tools package and not the nss-tools package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

NSS (Network Security Services) versions prior to 3.73 or 3.68.1 ESR are vulnerable to a heap overflow when handling DER-encoded DSA or RSA-PSS signatures. Applications using NSS for handling signatures encoded within CMS, S/MIME, PKCS #7, or PKCS #12 are likely to be impacted. Applications using NSS for certificate validation or other TLS, X.509, OCSP or CRL functionality may be impacted, depending on how they configure NSS. Note: This vulnerability does NOT impact Mozilla Firefox. However, email clients and PDF viewers that use NSS for signature verification, such as Thunderbird, LibreOffice, Evolution and Evince are believed to be impacted. This vulnerability affects NSS < 3.73 and NSS < 3.68.1.

Remediation

Upgrade Amazon-Linux:2018.03 nss-tools to version 0:3.53.1-7.87.amzn1 or higher.
This issue was patched in ALAS-2021-1552.

References

critical severity

SQL Injection

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.32.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.32.amzn1 or higher.
This issue was patched in ALAS-2023-1691.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-12.26.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.5, there is an integer overflow in storeRawNames.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-12.26.amzn1 or higher.
This issue was patched in ALAS-2022-1570.

References

high severity

Out-of-Bounds

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: ca-certificates
  • Introduced through: ca-certificates@2018.2.22-65.1.24.amzn1
  • Fixed in: 0:2018.2.22-65.1.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ca-certificates@2018.2.22-65.1.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ca-certificates package and not the ca-certificates package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes "e-Tugra" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from "e-Tugra" from the root store.

Remediation

Upgrade Amazon-Linux:2018.03 ca-certificates to version 0:2018.2.22-65.1.31.amzn1 or higher.
This issue was patched in ALAS-2023-1817.

References

high severity

SQL Injection

  • Vulnerable module: cyrus-sasl-lib
  • Introduced through: cyrus-sasl-lib@2.1.23-13.16.amzn1
  • Fixed in: 0:2.1.23-13.17.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources cyrus-sasl-lib@2.1.23-13.16.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream cyrus-sasl-lib package and not the cyrus-sasl-lib package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In Cyrus SASL 2.1.17 through 2.1.27 before 2.1.28, plugins/sql.c does not escape the password for a SQL INSERT or UPDATE statement.

Remediation

Upgrade Amazon-Linux:2018.03 cyrus-sasl-lib to version 0:2.1.23-13.17.amzn1 or higher.
This issue was patched in ALAS-2022-1574.

References

high severity

Incorrect Behavior Order: Early Validation

  • Vulnerable module: gzip
  • Introduced through: gzip@1.5-9.19.amzn1
  • Fixed in: 0:1.5-9.20.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources gzip@1.5-9.19.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gzip package and not the gzip package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Amazon-Linux:2018.03 gzip to version 0:1.5-9.20.amzn1 or higher.
This issue was patched in ALAS-2022-1590.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5-libs
  • Introduced through: krb5-libs@1.15.1-46.48.amzn1
  • Fixed in: 0:1.15.1-46.49.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources krb5-libs@1.15.1-46.48.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5-libs package and not the krb5-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Amazon-Linux:2018.03 krb5-libs to version 0:1.15.1-46.49.amzn1 or higher.
This issue was patched in ALAS-2023-1667.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5-libs
  • Introduced through: krb5-libs@1.15.1-46.48.amzn1
  • Fixed in: 0:1.15.1-55.51.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources krb5-libs@1.15.1-46.48.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5-libs package and not the krb5-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has "a similar bug."

Remediation

Upgrade Amazon-Linux:2018.03 krb5-libs to version 0:1.15.1-55.51.amzn1 or higher.
This issue was patched in ALAS-2023-1680.

References

high severity

Out-of-Bounds

  • Vulnerable module: nss
  • Introduced through: nss@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.88.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss package and not the nss package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes being mishandled. This vulnerability affects Firefox < 110, Thunderbird < 102.8, and Firefox ESR < 102.8.

Remediation

Upgrade Amazon-Linux:2018.03 nss to version 0:3.53.1-7.88.amzn1 or higher.
This issue was patched in ALAS-2023-1736.

References

high severity

Out-of-Bounds

  • Vulnerable module: nss-sysinit
  • Introduced through: nss-sysinit@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.88.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-sysinit@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-sysinit package and not the nss-sysinit package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes being mishandled. This vulnerability affects Firefox < 110, Thunderbird < 102.8, and Firefox ESR < 102.8.

Remediation

Upgrade Amazon-Linux:2018.03 nss-sysinit to version 0:3.53.1-7.88.amzn1 or higher.
This issue was patched in ALAS-2023-1736.

References

high severity

Out-of-Bounds

  • Vulnerable module: nss-tools
  • Introduced through: nss-tools@3.53.1-7.85.amzn1
  • Fixed in: 0:3.53.1-7.88.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-tools@3.53.1-7.85.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-tools package and not the nss-tools package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary memory writes via PKCS 12 Safe Bag attributes being mishandled. This vulnerability affects Firefox < 110, Thunderbird < 102.8, and Firefox ESR < 102.8.

Remediation

Upgrade Amazon-Linux:2018.03 nss-tools to version 0:3.53.1-7.88.amzn1 or higher.
This issue was patched in ALAS-2023-1736.

References

high severity

Incorrect Behavior Order: Early Validation

  • Vulnerable module: xz-libs
  • Introduced through: xz-libs@5.2.2-1.13.amzn1
  • Fixed in: 0:5.2.2-1.14.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources xz-libs@5.2.2-1.13.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream xz-libs package and not the xz-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An arbitrary file write vulnerability was found in GNU gzip's zgrep utility. When zgrep is applied on the attacker's chosen file name (for example, a crafted file name), this can overwrite an attacker's content to an arbitrary attacker-selected file. This flaw occurs due to insufficient validation when processing filenames with two or more newlines where selected content and the target file names are embedded in crafted multi-line file names. This flaw allows a remote, low privileged attacker to force zgrep to write arbitrary files on the system.

Remediation

Upgrade Amazon-Linux:2018.03 xz-libs to version 0:5.2.2-1.14.amzn1 or higher.
This issue was patched in ALAS-2022-1598.

References

high severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.148.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.148.amzn1 or higher.
This issue was patched in ALAS-2023-1876.

References

high severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.148.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.148.amzn1 or higher.
This issue was patched in ALAS-2023-1876.

References

high severity

Out-of-Bounds

  • Vulnerable module: zlib
  • Introduced through: zlib@1.2.8-7.18.amzn1
  • Fixed in: 0:1.2.8-7.19.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources zlib@1.2.8-7.18.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

Remediation

Upgrade Amazon-Linux:2018.03 zlib to version 0:1.2.8-7.19.amzn1 or higher.
This issue was patched in ALAS-2022-1602.

References

high severity

Use After Free

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-15.32.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-15.32.amzn1 or higher.
This issue was patched in ALAS-2022-1654.

References

high severity
new

Integer Overflow or Wraparound

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.27.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNOME GLib before 2.65.3 has an integer overflow, that might lead to an out-of-bounds write, in g_option_group_add_entries. NOTE: the vendor's position is "Realistically this is not a security issue. The standard pattern is for callers to provide a static list of option entries in a fixed number of calls to g_option_group_add_entries()." The researcher states that this pattern is undocumented

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.27.amzn1 or higher.
This issue was patched in ALAS-2024-1929.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses
  • Introduced through: ncurses@5.7-4.20090207.14.amzn1
  • Fixed in: 0:5.7-4.20090207.15.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ncurses@5.7-4.20090207.14.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Amazon-Linux:2018.03 ncurses to version 0:5.7-4.20090207.15.amzn1 or higher.
This issue was patched in ALAS-2023-1778.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses-base
  • Introduced through: ncurses-base@5.7-4.20090207.14.amzn1
  • Fixed in: 0:5.7-4.20090207.15.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ncurses-base@5.7-4.20090207.14.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses-base package and not the ncurses-base package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Amazon-Linux:2018.03 ncurses-base to version 0:5.7-4.20090207.15.amzn1 or higher.
This issue was patched in ALAS-2023-1778.

References

high severity

Out-of-bounds Write

  • Vulnerable module: ncurses-libs
  • Introduced through: ncurses-libs@5.7-4.20090207.14.amzn1
  • Fixed in: 0:5.7-4.20090207.15.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ncurses-libs@5.7-4.20090207.14.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses-libs package and not the ncurses-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.

Remediation

Upgrade Amazon-Linux:2018.03 ncurses-libs to version 0:5.7-4.20090207.15.amzn1 or higher.
This issue was patched in ALAS-2023-1778.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.149.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An XML External Entity (XXE) issue was discovered in Python through 3.9.1. The plistlib module no longer accepts entity declarations in XML plist files to avoid XML vulnerabilities.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.149.amzn1 or higher.
This issue was patched in ALAS-2023-1880.

References

high severity

XML External Entity (XXE) Injection

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.149.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An XML External Entity (XXE) issue was discovered in Python through 3.9.1. The plistlib module no longer accepts entity declarations in XML plist files to avoid XML vulnerabilities.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.149.amzn1 or higher.
This issue was patched in ALAS-2023-1880.

References

high severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: ca-certificates
  • Introduced through: ca-certificates@2018.2.22-65.1.24.amzn1
  • Fixed in: 0:2018.2.22-65.1.29.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ca-certificates@2018.2.22-65.1.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream ca-certificates package and not the ca-certificates package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.

Remediation

Upgrade Amazon-Linux:2018.03 ca-certificates to version 0:2018.2.22-65.1.29.amzn1 or higher.
This issue was patched in ALAS-2023-1690.

References

high severity

Use After Free

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-15.33.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situations.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-15.33.amzn1 or higher.
This issue was patched in ALAS-2022-1655.

References

high severity

Out-of-bounds Read

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c, related to utf8_str().

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

Out-of-bounds Read

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.24.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNOME GLib 2.56.1 has an out-of-bounds read vulnerability in g_markup_parse_context_parse() in gmarkup.c, related to utf8_str().

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.24.amzn1 or higher.
This issue was patched in ALAS-2023-1749.

References

high severity

Resource Exhaustion

  • Vulnerable module: libnghttp2
  • Introduced through: libnghttp2@1.33.0-1.1.6.amzn1
  • Fixed in: 0:1.33.0-1.1.7.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libnghttp2@1.33.0-1.1.6.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libnghttp2 package and not the libnghttp2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy’s HTTP/2 codec may leak a header map and bookkeeping structures upon receiving RST_STREAM immediately followed by the GOAWAY frames from an upstream server. In nghttp2, cleanup of pending requests due to receipt of the GOAWAY frame skips de-allocation of the bookkeeping structure and pending compressed header. The error return [code path] is taken if connection is already marked for not sending more requests due to GOAWAY frame. The clean-up code is right after the return statement, causing memory leak. Denial of service through memory exhaustion. This vulnerability was patched in versions(s) 1.26.3, 1.25.8, 1.24.9, 1.23.11.

Remediation

Upgrade Amazon-Linux:2018.03 libnghttp2 to version 0:1.33.0-1.1.7.amzn1 or higher.
This issue was patched in ALAS-2023-1793.

References

high severity

Resource Exhaustion

  • Vulnerable module: libnghttp2
  • Introduced through: libnghttp2@1.33.0-1.1.6.amzn1
  • Fixed in: 0:1.33.0-1.1.8.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libnghttp2@1.33.0-1.1.6.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libnghttp2 package and not the libnghttp2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Remediation

Upgrade Amazon-Linux:2018.03 libnghttp2 to version 0:1.33.0-1.1.8.amzn1 or higher.
This issue was patched in ALAS-2023-1869.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2
  • Introduced through: libssh2@1.4.2-3.12.amzn1
  • Fixed in: 0:1.4.2-3.14.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libssh2@1.4.2-3.12.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in function _libssh2_packet_add in libssh2 1.10.0 allows attackers to access out of bounds memory.

Remediation

Upgrade Amazon-Linux:2018.03 libssh2 to version 0:1.4.2-3.14.amzn1 or higher.
This issue was patched in ALAS-2023-1834.

References

high severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in ldap_X509dn2bv in OpenLDAP before 2.4.57 leading to a slapd crash in the X.509 DN parsing in ad_keystring, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Improper Handling of Length Parameter Inconsistency

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a memch->bv_len miscalculation and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to slapd crashes in the Certificate Exact Assertion processing, resulting in denial of service (schema_init.c serialNumberAndIssuerCheck).

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Integer Underflow

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An integer underflow was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Certificate List Exact Assertion processing, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Out-of-bounds Read

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Reachable Assertion

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an assertion failure in slapd in the saslAuthzTo validation, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Reachable Assertion

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_element, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Release of Invalid Pointer or Reference

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to an invalid pointer free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Release of Invalid Pointer or Reference

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was discovered in OpenLDAP before 2.4.57 leading to a double free and slapd crash in the saslAuthzTo processing, resulting in denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Resource Exhaustion

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In OpenLDAP through 2.4.57 and 2.5.x through 2.5.1alpha, an assertion failure in slapd can occur in the issuerAndThisUpdateCheck function via a crafted packet, resulting in a denial of service (daemon exit) via a short timestamp. This is related to schema_init.c and checkTime.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.156.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.156.amzn1 or higher.
This issue was patched in ALAS-2022-1575.

References

high severity

Use After Free

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.162.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.

The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.

This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.

Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.

The OpenSSL cms and smime command line applications are similarly affected.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.162.amzn1 or higher.
This issue was patched in ALAS-2023-1683.

References

high severity

Improper Input Validation

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.145.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.145.amzn1 or higher.
This issue was patched in ALAS-2023-1713.

References

high severity

Resource Exhaustion

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.145.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.145.amzn1 or higher.
This issue was patched in ALAS-2023-1713.

References

high severity

Improper Input Validation

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.145.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.145.amzn1 or higher.
This issue was patched in ALAS-2023-1713.

References

high severity

Resource Exhaustion

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.145.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.145.amzn1 or higher.
This issue was patched in ALAS-2023-1713.

References

high severity

Improper Access Control

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.36.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.36.amzn1 or higher.
This issue was patched in ALAS-2023-1741.

References

high severity

Incorrect Type Conversion or Cast

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.162.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.162.amzn1 or higher.
This issue was patched in ALAS-2023-1683.

References

high severity

Resource Exhaustion

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Rejected reason: Rejected by upstream.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

Resource Exhaustion

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Rejected reason: Rejected by upstream.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.44.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.44.amzn1 or higher.
This issue was patched in ALAS-2023-1874.

References

high severity

Use After Free

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.44.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.44.amzn1 or higher.
This issue was patched in ALAS-2023-1874.

References

high severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.162.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.162.amzn1 or higher.
This issue was patched in ALAS-2023-1683.

References

high severity

Information Exposure

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in glib before version 2.63.6. Due to random charset alias, pkexec can leak content from files owned by privileged users to unprivileged ones under the right condition.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

Out-of-Bounds

  • Vulnerable module: tar
  • Introduced through: tar@2:1.26-31.22.amzn1
  • Fixed in: 2:1.26-31.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources tar@2:1.26-31.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Remediation

Upgrade Amazon-Linux:2018.03 tar to version 2:1.26-31.23.amzn1 or higher.
This issue was patched in ALAS-2023-1704.

References

high severity

Link Following

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in GNOME GLib before 2.66.8. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION to replace a path that is a dangling symlink, it incorrectly also creates the target of the symlink as an empty file, which could conceivably have security relevance if the symlink is attacker-controlled. (If the path is a symlink to a file that already exists, then the contents of that file correctly remain unchanged.)

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

CVE-2017-10140

  • Vulnerable module: db4
  • Introduced through: db4@4.7.25-18.11.amzn1
  • Fixed in: 0:4.7.25-22.13.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources db4@4.7.25-18.11.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream db4 package and not the db4 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory.

Remediation

Upgrade Amazon-Linux:2018.03 db4 to version 0:4.7.25-22.13.amzn1 or higher.
This issue was patched in ALAS-2023-1726.

References

high severity

CVE-2017-10140

  • Vulnerable module: db4-utils
  • Introduced through: db4-utils@4.7.25-18.11.amzn1
  • Fixed in: 0:4.7.25-22.13.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources db4-utils@4.7.25-18.11.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream db4-utils package and not the db4-utils package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Postfix before 2.11.10, 3.0.x before 3.0.10, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 might allow local users to gain privileges by leveraging undocumented functionality in Berkeley DB 2.x and later, related to reading settings from DB_CONFIG in the current directory.

Remediation

Upgrade Amazon-Linux:2018.03 db4-utils to version 0:4.7.25-22.13.amzn1 or higher.
This issue was patched in ALAS-2023-1726.

References

high severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.23.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The keyfile settings backend in GNOME GLib (aka glib2.0) before 2.60.0 creates directories using g_file_make_directory_with_parents (kfsb->dir, NULL, NULL) and files using g_file_replace_contents (kfsb->file, contents, length, NULL, FALSE, G_FILE_CREATE_REPLACE_DESTINATION, NULL, NULL, NULL). Consequently, it does not properly restrict directory (and file) permissions. Instead, for directories, 0777 permissions are used; for files, default file permissions are used. This is similar to CVE-2019-12450.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.23.amzn1 or higher.
This issue was patched in ALAS-2023-1742.

References

high severity

CVE-2023-32803

  • Vulnerable module: ca-certificates
  • Introduced through: ca-certificates@2018.2.22-65.1.24.amzn1
  • Fixed in: 0:2018.2.22-65.1.30.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources ca-certificates@2018.2.22-65.1.24.amzn1

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Amazon-Linux:2018.03 ca-certificates to version 0:2018.2.22-65.1.30.amzn1 or higher.
This issue was patched in ALAS-2023-1795.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-12.25.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Expat (aka libexpat) before 2.4.4 has a signed integer overflow in XML_GetBuffer, for configurations with a nonzero XML_CONTEXT_BYTES.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-12.25.amzn1 or higher.
This issue was patched in ALAS-2022-1569.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.26.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PCRE before 8.38 mishandles the (?(<digits>) and (?(R<digits>) conditions, which allows remote attackers to cause a denial of service (integer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.26.amzn1 or higher.
This issue was patched in ALAS-2023-1775.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.26.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PCRE before 8.38 mishandles the [: and \ substrings in character classes, which allows remote attackers to cause a denial of service (uninitialized memory read) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.26.amzn1 or higher.
This issue was patched in ALAS-2023-1775.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre
  • Introduced through: pcre@8.21-7.8.amzn1
  • Fixed in: 0:8.21-7.9.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources pcre@8.21-7.8.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre package and not the pcre package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PCRE before 8.38 mishandles the (?(<digits>) and (?(R<digits>) conditions, which allows remote attackers to cause a denial of service (integer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.

Remediation

Upgrade Amazon-Linux:2018.03 pcre to version 0:8.21-7.9.amzn1 or higher.
This issue was patched in ALAS-2023-1767.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: pcre
  • Introduced through: pcre@8.21-7.8.amzn1
  • Fixed in: 0:8.21-7.9.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources pcre@8.21-7.8.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre package and not the pcre package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PCRE before 8.38 mishandles the [: and \ substrings in character classes, which allows remote attackers to cause a denial of service (uninitialized memory read) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.

Remediation

Upgrade Amazon-Linux:2018.03 pcre to version 0:8.21-7.9.amzn1 or higher.
This issue was patched in ALAS-2023-1767.

References

medium severity

Incorrect Calculation

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-12.28.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts function in xmlparse.c can lead to realloc misbehavior (e.g., allocating too few bytes, or only freeing memory).

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-12.28.amzn1 or higher.
This issue was patched in ALAS-2022-1588.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Use After Free

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Authentication

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Improper Authentication

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Use After Free

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-14.31.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for m_groupSize.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-14.31.amzn1 or higher.
This issue was patched in ALAS-2022-1603.

References

medium severity

Double Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Use After Free

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Double Free

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Use After Free

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.100.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.100.amzn1 or higher.
This issue was patched in ALAS-2021-1549.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Cleartext Transmission of Sensitive Information

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.100.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.100.amzn1 or higher.
This issue was patched in ALAS-2021-1549.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

libcurl provides the CURLOPT_CERTINFO option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt
  • Introduced through: libgcrypt@1.5.3-12.19.amzn1
  • Fixed in: 0:1.5.3-12.20.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libgcrypt@1.5.3-12.19.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt package and not the libgcrypt package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.

Remediation

Upgrade Amazon-Linux:2018.03 libgcrypt to version 0:1.5.3-12.20.amzn1 or higher.
This issue was patched in ALAS-2022-1578.

References

medium severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Eval Injection

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Eval Injection

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In Python 3 through 3.9.0, the Lib/test/multibytecodec_support.py CJK codec tests call eval() on content retrieved via HTTP.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.154.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.154.amzn1 or higher.
This issue was patched in ALAS-2021-1541.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: openldap
  • Introduced through: openldap@2.4.40-16.31.amzn1
  • Fixed in: 0:2.4.40-16.37.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openldap@2.4.40-16.31.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.

Remediation

Upgrade Amazon-Linux:2018.03 openldap to version 0:2.4.40-16.37.amzn1 or higher.
This issue was patched in ALAS-2023-1804.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc
  • Introduced through: glibc@2.17-324.188.amzn1
  • Fixed in: 0:2.17-324.189.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glibc@2.17-324.188.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Amazon-Linux:2018.03 glibc to version 0:2.17-324.189.amzn1 or higher.
This issue was patched in ALAS-2022-1576.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc
  • Introduced through: glibc@2.17-324.188.amzn1
  • Fixed in: 0:2.17-324.189.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glibc@2.17-324.188.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its path argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Amazon-Linux:2018.03 glibc to version 0:2.17-324.189.amzn1 or higher.
This issue was patched in ALAS-2022-1576.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc-common
  • Introduced through: glibc-common@2.17-324.188.amzn1
  • Fixed in: 0:2.17-324.189.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glibc-common@2.17-324.188.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc-common package and not the glibc-common package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The deprecated compatibility function clnt_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its hostname argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Amazon-Linux:2018.03 glibc-common to version 0:2.17-324.189.amzn1 or higher.
This issue was patched in ALAS-2022-1576.

References

medium severity

Improper Input Validation

  • Vulnerable module: glibc-common
  • Introduced through: glibc-common@2.17-324.188.amzn1
  • Fixed in: 0:2.17-324.189.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glibc-common@2.17-324.188.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc-common package and not the glibc-common package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The deprecated compatibility function svcunix_create in the sunrpc module of the GNU C Library (aka glibc) through 2.34 copies its path argument on the stack without validating its length, which may result in a buffer overflow, potentially resulting in a denial of service or (if an application is not built with a stack protector enabled) arbitrary code execution.

Remediation

Upgrade Amazon-Linux:2018.03 glibc-common to version 0:2.17-324.189.amzn1 or higher.
This issue was patched in ALAS-2022-1576.

References

medium severity

Out-of-Bounds

  • Vulnerable module: zlib
  • Introduced through: zlib@1.2.8-7.18.amzn1
  • Fixed in: 0:1.2.8-7.20.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources zlib@1.2.8-7.18.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).

Remediation

Upgrade Amazon-Linux:2018.03 zlib to version 0:1.2.8-7.20.amzn1 or higher.
This issue was patched in ALAS-2022-1650.

References

medium severity

Arbitrary Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.158.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.158.amzn1 or higher.
This issue was patched in ALAS-2022-1605.

References

medium severity

Arbitrary Command Injection

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.159.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.159.amzn1 or higher.
This issue was patched in ALAS-2022-1626.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat
  • Introduced through: expat@2.1.0-12.24.amzn1
  • Fixed in: 0:2.1.0-15.34.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources expat@2.1.0-12.24.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function.

Remediation

Upgrade Amazon-Linux:2018.03 expat to version 0:2.1.0-15.34.amzn1 or higher.
This issue was patched in ALAS-2023-1882.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: krb5-libs
  • Introduced through: krb5-libs@1.15.1-46.48.amzn1
  • Fixed in: 0:1.15.1-55.52.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources krb5-libs@1.15.1-46.48.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream krb5-libs package and not the krb5-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.

Remediation

Upgrade Amazon-Linux:2018.03 krb5-libs to version 0:1.15.1-55.52.amzn1 or higher.
This issue was patched in ALAS-2023-1818.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Out-of-Bounds

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.43.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.43.amzn1 or higher.
This issue was patched in ALAS-2023-1841.

References

medium severity

Resource Exhaustion

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Out-of-Bounds

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.43.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the product does not support the legacy SAX1 interface with custom callbacks; there is a crash even without crafted input.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.43.amzn1 or higher.
This issue was patched in ALAS-2023-1841.

References

medium severity

Resource Exhaustion

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Information Exposure

  • Vulnerable module: nss-softokn
  • Introduced through: nss-softokn@3.53.1-6.46.amzn1
  • Fixed in: 0:3.53.1-6.48.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-softokn@3.53.1-6.46.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-softokn package and not the nss-softokn package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The NSS code used for checking PKCS#1 v1.5 was leaking information useful in mounting Bleichenbacher-like attacks. Both the overall correctness of the padding as well as the length of the encrypted message was leaking through timing side-channel. By sending large number of attacker-selected ciphertexts, the attacker would be able to decrypt a previously intercepted PKCS#1 v1.5 ciphertext (for example, to decrypt a TLS session that used RSA key exchange), or forge a signature using the victim's key. The issue was fixed by implementing the implicit rejection algorithm, in which the NSS returns a deterministic random message in case invalid padding is detected, as proposed in the Marvin Attack paper. This vulnerability affects NSS < 3.61.

Remediation

Upgrade Amazon-Linux:2018.03 nss-softokn to version 0:3.53.1-6.48.amzn1 or higher.
This issue was patched in ALAS-2023-1858.

References

medium severity

Information Exposure

  • Vulnerable module: nss-softokn
  • Introduced through: nss-softokn@3.53.1-6.46.amzn1
  • Fixed in: 0:3.53.1-6.49.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-softokn@3.53.1-6.46.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-softokn package and not the nss-softokn package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

NSS was susceptible to a timing side-channel attack when performing RSA decryption. This attack could potentially allow an attacker to recover the private data. This vulnerability affects Firefox < 124, Firefox ESR < 115.9, and Thunderbird < 115.9.

Remediation

Upgrade Amazon-Linux:2018.03 nss-softokn to version 0:3.53.1-6.49.amzn1 or higher.
This issue was patched in ALAS-2024-1907.

References

medium severity

Information Exposure

  • Vulnerable module: nss-softokn-freebl
  • Introduced through: nss-softokn-freebl@3.53.1-6.46.amzn1
  • Fixed in: 0:3.53.1-6.48.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-softokn-freebl@3.53.1-6.46.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-softokn-freebl package and not the nss-softokn-freebl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The NSS code used for checking PKCS#1 v1.5 was leaking information useful in mounting Bleichenbacher-like attacks. Both the overall correctness of the padding as well as the length of the encrypted message was leaking through timing side-channel. By sending large number of attacker-selected ciphertexts, the attacker would be able to decrypt a previously intercepted PKCS#1 v1.5 ciphertext (for example, to decrypt a TLS session that used RSA key exchange), or forge a signature using the victim's key. The issue was fixed by implementing the implicit rejection algorithm, in which the NSS returns a deterministic random message in case invalid padding is detected, as proposed in the Marvin Attack paper. This vulnerability affects NSS < 3.61.

Remediation

Upgrade Amazon-Linux:2018.03 nss-softokn-freebl to version 0:3.53.1-6.48.amzn1 or higher.
This issue was patched in ALAS-2023-1858.

References

medium severity

Information Exposure

  • Vulnerable module: nss-softokn-freebl
  • Introduced through: nss-softokn-freebl@3.53.1-6.46.amzn1
  • Fixed in: 0:3.53.1-6.49.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources nss-softokn-freebl@3.53.1-6.46.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream nss-softokn-freebl package and not the nss-softokn-freebl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

NSS was susceptible to a timing side-channel attack when performing RSA decryption. This attack could potentially allow an attacker to recover the private data. This vulnerability affects Firefox < 124, Firefox ESR < 115.9, and Thunderbird < 115.9.

Remediation

Upgrade Amazon-Linux:2018.03 nss-softokn-freebl to version 0:3.53.1-6.49.amzn1 or higher.
This issue was patched in ALAS-2024-1907.

References

medium severity

Resource Exhaustion

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.163.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.

Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.

An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.

When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).

With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.

Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.

Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.

In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.

The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.

In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.163.amzn1 or higher.
This issue was patched in ALAS-2023-1762.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client. The greatest threat that this flaw poses is to application availability.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in python. An improperly handled HTTP response in the HTTP client code of python may allow a remote attacker, who controls the HTTP server, to make the client script enter an infinite loop, consuming CPU time. The highest threat from this vulnerability is to system availability.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Resource Exhaustion

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

There's a flaw in urllib's AbstractBasicAuthHandler class. An attacker who controls a malicious HTTP server that an HTTP client (such as web browser) connects to, could trigger a Regular Expression Denial of Service (ReDOS) during an authentication request with a specially crafted payload that is sent by the server to the client. The greatest threat that this flaw poses is to application availability.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.100.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.100.amzn1 or higher.
This issue was patched in ALAS-2021-1549.

References

medium severity

Insufficient Verification of Data Authenticity

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.100.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got before the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.100.amzn1 or higher.
This issue was patched in ALAS-2021-1549.

References

medium severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnupg2
  • Introduced through: gnupg2@2.0.28-2.34.amzn1
  • Fixed in: 0:2.0.28-2.35.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources gnupg2@2.0.28-2.34.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.

Remediation

Upgrade Amazon-Linux:2018.03 gnupg2 to version 0:2.0.28-2.35.amzn1 or higher.
This issue was patched in ALAS-2022-1630.

References

medium severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Authentication Bypass by Primary Weakness

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Use After Free

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A use after free vulnerability exists in curl <7.87.0. Curl can be asked to tunnel virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value).

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2 package and not the libxml2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Improper Input Validation

  • Vulnerable module: libxml2-python27
  • Introduced through: libxml2-python27@2.9.1-6.4.41.amzn1
  • Fixed in: 0:2.9.1-6.6.42.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libxml2-python27@2.9.1-6.4.41.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libxml2-python27 package and not the libxml2-python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there is an attempt to use the first byte of an empty string, and any value is possible (not solely the '\0' value).

Remediation

Upgrade Amazon-Linux:2018.03 libxml2-python27 to version 0:2.9.1-6.6.42.amzn1 or higher.
This issue was patched in ALAS-2023-1743.

References

medium severity

Resource Exhaustion

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.163.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A security vulnerability has been identified in all supported versions

of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.163.amzn1 or higher.
This issue was patched in ALAS-2023-1762.

References

medium severity

HTTP Request Smuggling

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

HTTP Request Smuggling

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Improper Enforcement of Message Integrity During Transmission in a Communication Channel

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Improper Enforcement of Message Integrity During Transmission in a Communication Channel

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Excessive Iteration

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.164.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.164.amzn1 or higher.
This issue was patched in ALAS-2023-1843.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.163.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.

As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.

Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.

Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.163.amzn1 or higher.
This issue was patched in ALAS-2023-1762.

References

medium severity

Improper Certificate Validation

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.163.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.

Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.

Policy processing is disabled by default but can be enabled by passing the -policy&#39; argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.163.amzn1 or higher.
This issue was patched in ALAS-2023-1762.

References

medium severity

Missing Required Cryptographic Step

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.165.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.165.amzn1 or higher.
This issue was patched in ALAS-2023-1891.

References

medium severity

Resource Exhaustion

  • Vulnerable module: openssl
  • Introduced through: openssl@1:1.0.2k-16.153.amzn1
  • Fixed in: 1:1.0.2k-16.164.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources openssl@1:1.0.2k-16.153.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

Remediation

Upgrade Amazon-Linux:2018.03 openssl to version 1:1.0.2k-16.164.amzn1 or higher.
This issue was patched in ALAS-2023-1843.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in Python, specifically within the urllib.parse module. This module helps break Uniform Resource Locator (URL) strings into components. The issue involves how the urlparse method does not sanitize input and allows characters like '\r' and '\n' in the URL path. This flaw allows an attacker to input a crafted URL, leading to injection attacks. This flaw affects Python versions prior to 3.10.0b1, 3.9.5, 3.8.11, 3.7.11 and 3.6.14.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Unchecked Return Value

  • Vulnerable module: python27
  • Introduced through: python27@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27 package and not the python27 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in Python, specifically in the FTP (File Transfer Protocol) client library in PASV (passive) mode. The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.

Remediation

Upgrade Amazon-Linux:2018.03 python27 to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in Python, specifically within the urllib.parse module. This module helps break Uniform Resource Locator (URL) strings into components. The issue involves how the urlparse method does not sanitize input and allows characters like '\r' and '\n' in the URL path. This flaw allows an attacker to input a crafted URL, leading to injection attacks. This flaw affects Python versions prior to 3.10.0b1, 3.9.5, 3.8.11, 3.7.11 and 3.6.14.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Unchecked Return Value

  • Vulnerable module: python27-libs
  • Introduced through: python27-libs@2.7.18-2.141.amzn1
  • Fixed in: 0:2.7.18-2.142.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources python27-libs@2.7.18-2.141.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream python27-libs package and not the python27-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A flaw was found in Python, specifically in the FTP (File Transfer Protocol) client library in PASV (passive) mode. The issue is how the FTP client trusts the host from the PASV response by default. This flaw allows an attacker to set up a malicious FTP server that can trick FTP clients into connecting back to a given IP address and port. This vulnerability could lead to FTP client scanning ports, which otherwise would not have been possible.

Remediation

Upgrade Amazon-Linux:2018.03 python27-libs to version 0:2.7.18-2.142.amzn1 or higher.
This issue was patched in ALAS-2022-1593.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libssh2
  • Introduced through: libssh2@1.4.2-3.12.amzn1
  • Fixed in: 0:1.4.2-3.13.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libssh2@1.4.2-3.12.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the _libssh2_packet_require and _libssh2_packet_requirev functions. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Amazon-Linux:2018.03 libssh2 to version 0:1.4.2-3.13.amzn1 or higher.
This issue was patched in ALAS-2023-1756.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libssh2
  • Introduced through: libssh2@1.4.2-3.12.amzn1
  • Fixed in: 0:1.4.2-3.13.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libssh2@1.4.2-3.12.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libssh2 package and not the libssh2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFTP packets with empty payloads are parsed. A remote attacker who compromises a SSH server may be able to cause a Denial of Service or read data in the client memory.

Remediation

Upgrade Amazon-Linux:2018.03 libssh2 to version 0:1.4.2-3.13.amzn1 or higher.
This issue was patched in ALAS-2023-1756.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Special Element Injection

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.26.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Heap-based buffer overflow in the find_fixedlength function in pcre_compile.c in PCRE before 8.38 allows remote attackers to cause a denial of service (crash) or obtain sensitive information from heap memory and possibly bypass the ASLR protection mechanism via a crafted regular expression with an excess closing parenthesis.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.26.amzn1 or higher.
This issue was patched in ALAS-2023-1775.

References

medium severity

Insufficiently Protected Credentials

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Special Element Injection

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.105.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.105.amzn1 or higher.
This issue was patched in ALAS-2023-1727.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: pcre
  • Introduced through: pcre@8.21-7.8.amzn1
  • Fixed in: 0:8.21-7.9.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources pcre@8.21-7.8.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre package and not the pcre package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

Heap-based buffer overflow in the find_fixedlength function in pcre_compile.c in PCRE before 8.38 allows remote attackers to cause a denial of service (crash) or obtain sensitive information from heap memory and possibly bypass the ASLR protection mechanism via a crafted regular expression with an excess closing parenthesis.

Remediation

Upgrade Amazon-Linux:2018.03 pcre to version 0:8.21-7.9.amzn1 or higher.
This issue was patched in ALAS-2023-1767.

References

medium severity

Directory Traversal

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

Buffer Overflow

  • Vulnerable module: glib2
  • Introduced through: glib2@2.36.3-5.22.amzn1
  • Fixed in: 0:2.36.3-5.25.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources glib2@2.36.3-5.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream glib2 package and not the glib2 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

PCRE before 8.38 mishandles the interaction of lookbehind assertions and mutually recursive subpatterns, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.

Remediation

Upgrade Amazon-Linux:2018.03 glib2 to version 0:2.36.3-5.25.amzn1 or higher.
This issue was patched in ALAS-2023-1769.

References

medium severity

Directory Traversal

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.104.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.104.amzn1 or higher.
This issue was patched in ALAS-2023-1729.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@2:1.26-31.22.amzn1
  • Fixed in: 2:1.26-31.24.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources tar@2:1.26-31.22.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

Remediation

Upgrade Amazon-Linux:2018.03 tar to version 2:1.26-31.24.amzn1 or higher.
This issue was patched in ALAS-2023-1755.

References

medium severity

Improper Validation of Syntactic Correctness of Input

  • Vulnerable module: curl
  • Introduced through: curl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources curl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Amazon-Linux:2018.03 curl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References

medium severity

Improper Validation of Syntactic Correctness of Input

  • Vulnerable module: libcurl
  • Introduced through: libcurl@7.61.1-12.99.amzn1
  • Fixed in: 0:7.61.1-12.101.amzn1

Detailed paths

  • Introduced through: amazonlinux@2018.03.0.20211001.0-with-sources libcurl@7.61.1-12.99.amzn1

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2018.03 relevant fixed versions and status.

When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings.

Remediation

Upgrade Amazon-Linux:2018.03 libcurl to version 0:7.61.1-12.101.amzn1 or higher.
This issue was patched in ALAS-2022-1646.

References