Repository navigation
[GHSA-2mjx-qc3c-rqvc] Rustls: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries - #10683
Conversation
|
Hi there @ctz! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
There was a problem hiding this comment.
🟢 Approval recommended
The upstream release confirms the reference’s relevance, and the limited metadata changes introduce no identified issues.
No open issues 🎉
What changed in this PR
Improves remediation traceability for GHSA-2mjx-qc3c-rqvc by linking its advisory entry to the official Rustls 0.23.45 security release.
Changes:
- Adds the upstream release-notes URL, which explicitly identifies this advisory.
- Advances the
modifiedtimestamp; affected versions, severity, and vulnerability details remain unchanged.
| File | Description |
|---|---|
| advisories/github-reviewed/2026/10/GHSA-2mjx-qc3c-rqvc/GHSA-2mjx-qc3c-rqvc.json | Adds the security-release reference and updates the modification timestamp. |
Review effort: Max
Updates
Comments
Reason for Change
Add the official upstream
rustlsv0.23.45 security-release reference to GHSA-2mjx-qc3c-rqvc.Supporting Evidence
The official rustls v0.23.45 release notes identify GHSA-2mjx-qc3c-rqvc and document the remediation for improper TLS 1.3 handshake-message handling across encryption-level boundaries.
The advisory already references the corresponding upstream fix commit and RustSec advisory.
Justification
Adding the official patched-release reference provides direct, maintainer-controlled evidence identifying the release containing the security fix. This improves traceability and helps developers verify the remediation.
Scope: Reference-only improvement. No changes to affected-package metadata, vulnerable or patched version ranges, vulnerability description, CWE classifications, severity, or CVSS scoring.