Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Update release notes #5346

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: Update release notes #5346

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9d6e7ad
docs: Update release notes
Dan-Heath Dec 10, 2024
19cd2cc
docs: Clarify affected versions, fix spacing
Dan-Heath Dec 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions website/content/docs/release-notes/v0_16_0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -312,6 +312,25 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
0.8.0+ (Fixed in Boundary Community Edition and Boundary Enterprise 0.16.4, 0.17.3, 0.18.2)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does 0.8.0+ mean here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the review! It is intended to show that the issue was present in versions 0.8.0 and forward (which I got from the CVE ticket). It does look a little out of place here since it's such an early version. Maybe we should display that as 0.8.0 - 0.16.3 instead?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that might be more easily understandable!

</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>

Expand Down
19 changes: 19 additions & 0 deletions website/content/docs/release-notes/v0_17_0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,5 +218,24 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
0.8.0+ (Fixed in Boundary Community Edition and Boundary Enterprise 0.16.4, 0.17.3, 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>
36 changes: 36 additions & 0 deletions website/content/docs/release-notes/v0_18_0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,5 +186,41 @@ description: >-
</td>
</tr>

<tr>
<td style={{verticalAlign: 'middle'}}>
0.18.0 (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+ (Fixed in Boundary Community Edition and Boundary Enterprise 0.16.4, 0.17.3, 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>
Loading