CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Update release notes (#5346)

Browse Source 
* docs: Update release notes

* docs: Clarify affected versions, fix spacing
This commit is contained in:
Dan Heath authored and GitHub committed 2024-12-16 15:29:37 -05:00
1 parent fd8f0c1cc6
commit b2bcd8f7be
3 files changed
+91 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/release-notes/v0_16_0.mdx
+21
View File
@@ -312,6 +312,27 @@ description: >-
</td>
</tr>
<tr>
<td style={{verticalAlign: 'middle'}}>
0.8.0 - 0.16.3
<br /><br />
(Fixed in Boundary Community Edition and Boundary Enterprise 0.16.4)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary controller incorrectly handles HTTP requests and stops prematurely (HCSEC-2024-28)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary Community Edition and Boundary Enterprise incorrectly handle HTTP requests while the Boundary controller is starting up, which may cause the controller to stop prematurely. Boundary is only vulnerable to this flaw during the controller's initialization, which usually occurs in milliseconds during Boundary's startup process.
<br /><br />
This vulnerability, HCSEC-2024-28, is fixed in Boundary Community Edition and Boundary Enterprise versions 0.16.4, 0.17.3, and 0.18.2.
<br /><br />
Learn more: <a href="https://discuss.hashicorp.com/t/hcsec-2024-28-boundary-controller-incorrectly-handles-http-requests-on-initialization-which-may-lead-to-a-denial-of-service">HCSEC-2024-28: Boundary controller incorrectly handles http requests on initialization which may lead to a denial of service</a>
<br /><br />
<a href="/boundary/tutorials/self-managed-deployment/upgrade-version">Upgrade to the latest version of Boundary</a>
</td>
</tr>
</tbody>
</table>
website/content/docs/release-notes/v0_17_0.mdx
+27 -2
View File
@@ -184,7 +184,9 @@ description: >-
<tr>
<td style={{verticalAlign: 'middle'}}>
0.17.0 (Fixed in 0.17.1)
0.17.0
<br /><br />
(Fixed in 0.17.1)
</td>
<td style={{verticalAlign: 'middle'}}>
Using an invalid alias results in a 401 message
@@ -202,7 +204,9 @@ description: >-
<tr>
<td style={{verticalAlign: 'middle'}}>
0.17.0 (Fixed in 0.17.1)
0.17.0
<br /><br />
(Fixed in 0.17.1)
</td>
<td style={{verticalAlign: 'middle'}}>
Session recording fails when you use Secure File Copy (SCP)
@@ -218,5 +222,26 @@ description: >-
</td>
</tr>
<tr>
<td style={{verticalAlign: 'middle'}}>
0.8.0 - 0.17.2
<br /><br />
(Fixed in Boundary Community Edition and Boundary Enterprise 0.17.3)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary controller incorrectly handles HTTP requests and stops prematurely (HCSEC-2024-28)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary Community Edition and Boundary Enterprise incorrectly handle HTTP requests while the Boundary controller is starting up, which may cause the controller to stop prematurely. Boundary is only vulnerable to this flaw during the controller's initialization, which usually occurs in milliseconds during Boundary's startup process.
<br /><br />
This vulnerability, HCSEC-2024-28, is fixed in Boundary Community Edition and Boundary Enterprise versions 0.16.4, 0.17.3, and 0.18.2.
<br /><br />
Learn more: <a href="https://discuss.hashicorp.com/t/hcsec-2024-28-boundary-controller-incorrectly-handles-http-requests-on-initialization-which-may-lead-to-a-denial-of-service">HCSEC-2024-28: Boundary controller incorrectly handles http requests on initialization which may lead to a denial of service</a>
<br /><br />
<a href="/boundary/tutorials/self-managed-deployment/upgrade-version">Upgrade to the latest version of Boundary</a>
</td>
</tr>
</tbody>
</table>
website/content/docs/release-notes/v0_18_0.mdx
+43 -1
View File
@@ -170,7 +170,9 @@ description: >-
<tr>
<td style={{verticalAlign: 'middle'}}>
0.18.0 (Fixed in 0.18.1)
0.18.0
<br /><br />
(Fixed in 0.18.1)
</td>
<td style={{verticalAlign: 'middle'}}>
Users are incorrectly removed from managed groups
@@ -186,5 +188,45 @@ description: >-
</td>
</tr>
<tr>
<td style={{verticalAlign: 'middle'}}>
0.18.0
<br /><br />
(Fixed in 0.18.2)
</td>
<td style={{verticalAlign: 'middle'}}>
Session recordings fail with an error
</td>
<td style={{verticalAlign: 'middle'}}>
When large numbers of sessions were created around the same time using the AssumeRole API, the AWS STS (Security Token Service) credentials sometimes failed to refresh and session recordings would fail. The failure occurred due to throttling from AWS.
<br /><br />
Version 0.18.2 adds a cache for Amazon S3 clients to store temporary credentials and prevent AWS resources from being overwhelmed. This issue is now resolved.
<br /><br />
Learn more:&nbsp; <a href="/boundary/docs/configuration/session-recording/storage-providers/configure-s3">Configure Amazon S3 as a storage provider</a>
<br /><br />
<a href="/boundary/tutorials/self-managed-deployment/upgrade-version">Upgrade to the latest version of Boundary</a>
</td>
</tr>
<tr>
<td style={{verticalAlign: 'middle'}}>
0.8.0 - 0.18.1
<br /><br />
(Fixed in Boundary Community Edition and Boundary Enterprise 0.18.2)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary controller incorrectly handles HTTP requests and stops prematurely (HCSEC-2024-28)
</td>
<td style={{verticalAlign: 'middle'}}>
Boundary Community Edition and Boundary Enterprise incorrectly handle HTTP requests while the Boundary controller is starting up, which may cause the controller to stop prematurely. Boundary is only vulnerable to this flaw during the controller's initialization, which usually occurs in milliseconds during Boundary's startup process.
<br /><br />
This vulnerability, HCSEC-2024-28, is fixed in Boundary Community Edition and Boundary Enterprise versions 0.16.4, 0.17.3, and 0.18.2.
<br /><br />
Learn more: <a href="https://discuss.hashicorp.com/t/hcsec-2024-28-boundary-controller-incorrectly-handles-http-requests-on-initialization-which-may-lead-to-a-denial-of-service">HCSEC-2024-28: Boundary controller incorrectly handles http requests on initialization which may lead to a denial of service</a>
<br /><br />
<a href="/boundary/tutorials/self-managed-deployment/upgrade-version">Upgrade to the latest version of Boundary</a>
</td>
</tr>
</tbody>
</table>