Skip to content

Commit

Permalink
docs: update CVE Layout Changes (#3524) (#3535)
Browse files Browse the repository at this point in the history
* docs: first entry

* Update cve-2020-1971.md

* Update prisma-2022-0227.md

Updated CVE

* Update cve-2021-3449.md

Updated CVE

* Update cve-2021-3711.md

* Update cve-2022-25883.md

Updating CVE

* Update cve-2021-45079.md

* Updating CVEs

* Updating CVEs

* chore: prettier

---------

Co-authored-by: frederickjoi <[email protected]>
Co-authored-by: Karl Cardenas <[email protected]>
(cherry picked from commit 364f54c)

Co-authored-by: JamieM-Spectro <[email protected]>
  • Loading branch information
1 parent 89a7e37 commit fed8e71
Show file tree
Hide file tree
Showing 21 changed files with 542 additions and 102 deletions.
28 changes: 23 additions & 5 deletions docs/docs-content/security-bulletins/reports/cve-2015-8855.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,28 @@ toc_max_heading_level: 2
tags: ["security", "cve"]
---

# CVE Details
## CVE Details

We provide the most up-to-date information below.
[CVE-2015-8855](https://nvd.nist.gov/vuln/detail/CVE-2015-8855)

| CVE ID | Last Update | NIST CVE Summary | Our Official Summary | CVE Severity | Status |
| --------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------- |
| [CVE-2015-8855](https://nvd.nist.gov/vuln/detail/CVE-2015-8855) | 7/16/24 | The semver package before 4.3.2 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka a "regular expression denial of service (ReDoS)." | This is a false positive as the CVE is in a node.js package that has the same name which is being used in the Golang application. | [7.5](https://nvd.nist.gov/vuln/detail/CVE-2015-8855) | Ongoing |
## Last Update

7/31/2024

## NIST CVE Summary

The semver package before 4.3.2 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long
version string, aka a "regular expression denial of service (ReDoS)."

## Our Official Summary

This is a false positive as the CVE is in a node.js package that has the same name which is being used in the Golang
application.

## CVE Severity

[7.5](https://nvd.nist.gov/vuln/detail/CVE-2015-8855)

## Status

Ongoing
44 changes: 39 additions & 5 deletions docs/docs-content/security-bulletins/reports/cve-2020-1971.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,44 @@ toc_max_heading_level: 2
tags: ["security", "cve"]
---

# CVE Details
## CVE Details

We provide the most up-to-date information below.
[CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971)

| CVE ID | Last Update | NIST CVE Summary | Our Official Summary | CVE Severity | Status |
| --------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------- |
| [CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971) | 7/16/24 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w). | This is a false positive reported by twistlock. We have confirmed this CVE is fixed in the FIPS openSSL version 1.1.1f-1ubuntu2.fips.22 that’s being used in VerteX. You learn more at https://ubuntu.com/security/CVE-2020-1971. | [5.9](https://nvd.nist.gov/vuln/detail/CVE-2020-1971) | Ongoing |
## Last Update

7/16/2024

## NIST CVE Summary

The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known
as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to
see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL
pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the
GENERAL_NAME_cmp function for two purposes: 1\) Comparing CRL distribution point names between an available CRL and a
CRL distribution point embedded in an X509 certificate 2\) When verifying that a timestamp response token signer matches
the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an
attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can
trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that
some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to
the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for
the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work
against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct
correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser
will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other
OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in
OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

## Our Official Summary

This is a false positive reported by twistlock. We have confirmed this CVE is fixed in the FIPS openSSL version
1.1.1f-1ubuntu2.fips.22 that’s being used in VerteX. You learn more at
[https://ubuntu.com/security/CVE-2020-1971](https://ubuntu.com/security/CVE-2020-1971).

## CVE Severity

[5.9](https://nvd.nist.gov/vuln/detail/CVE-2020-1971)

## Status

Ongoing
34 changes: 29 additions & 5 deletions docs/docs-content/security-bulletins/reports/cve-2021-3449.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,34 @@ toc_max_heading_level: 2
tags: ["security", "cve"]
---

# CVE Details
## CVE Details

We provide the most up-to-date information below.
[CVE-2021-3449](https://nvd.nist.gov/vuln/detail/CVE-2021-3449)

| CVE ID | Last Update | NIST CVE Summary | Our Official Summary | CVE Severity | Status |
| --------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------- |
| [CVE-2021-3449](https://nvd.nist.gov/vuln/detail/CVE-2021-3449) | 7/16/24 | An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j). | This is a false positive reported by twistlock. We have confirmed this CVE is fixed in the FIPS openSSL version 1.1.1f-1ubuntu2.fips.22 that’s being used in VerteX. You can learn more at https://ubuntu.com/security/CVE-2021-3449. | [5.9](https://nvd.nist.gov/vuln/detail/CVE-2021-3449) | Ongoing |
## Last Update

7/16/2024

## NIST CVE Summary

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a
TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial
ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to
a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which
is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are
affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this
issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).

## Our Official Summary

This is a false positive reported by twistlock. We have confirmed this CVE is fixed in the FIPS openSSL version
1.1.1f-1ubuntu2.fips.22 that’s being used in VerteX. You can learn more at
[https://ubuntu.com/security/CVE-2021-3449](https://ubuntu.com/security/CVE-2021-3449).

## CVE Severity

[5.9](https://nvd.nist.gov/vuln/detail/CVE-2021-3449)

## Status

Ongoing
Loading

0 comments on commit fed8e71

Please sign in to comment.