# CVE-2022-30629: Session tickets lack random ticket_age_add in crypto/tls > An attacker observing TLS handshakes can correlate successive connections by comparing ticket ages due to non-random ticket_age_add values in Go's crypto/tls. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Aug 2022 - **Updated:** 6 Mar 2026 - **Also known as:** AZL-10550, BIT-golang-2022-30629, DEBIAN-CVE-2022-30629, GHSA-j55j-52j7-vq87, GO-2022-0531, MGASA-2022-0231, RHSA-2022:6102, RHSA-2022:6535, UBUNTU-CVE-2022-30629 ## What is CVE-2022-30629? CVE-2022-30629 is a low-severity vulnerability in Golang Go, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Non-random values for ticket_age_add in session tickets in crypto/tls before Go 1.17.11 and Go 1.18.3 allow an attacker that can observe TLS handshakes to correlate successive connections by comparing ticket ages during session resumption. Weakness: CWE-330 (Use of Insufficiently Random Values) ## Which versions are affected by CVE-2022-30629? 2 open source packages ship an affected version, including golang and stdlib. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang` | Bitnami | All versions | 1.17.11, 1.18.3 | | `stdlib` | Go | All versions | 1.17.11, 1.18.3 | | `butane` | Red Hat:openshift:4.11::el8 | All versions | 0:0.15.0-2.rhaos4.11.el8 | | `butane-debuginfo` | Red Hat:openshift:4.11::el8 | All versions | 0:0.15.0-2.rhaos4.11.el8 | | `butane-debugsource` | Red Hat:openshift:4.11::el8 | All versions | 0:0.15.0-2.rhaos4.11.el8 | | `butane-redistributable` | Red Hat:openshift:4.11::el8 | All versions | 0:0.15.0-2.rhaos4.11.el8 | | `cri-o` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-4.rhaos4.11.gitd6283df.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-4.rhaos4.11.gitd6283df.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-4.rhaos4.11.gitd6283df.el8 | | `cri-tools` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-6.el8 | | `cri-tools-debuginfo` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-6.el8 | | `cri-tools-debugsource` | Red Hat:openshift:4.11::el8 | All versions | 0:1.24.2-6.el8 | | `ignition` | Red Hat:openshift:4.11::el8 | All versions | 0:2.14.0-4.rhaos4.11.el8 | | `ignition-debuginfo` | Red Hat:openshift:4.11::el8 | All versions | 0:2.14.0-4.rhaos4.11.el8 | | `ignition-debugsource` | Red Hat:openshift:4.11::el8 | All versions | 0:2.14.0-4.rhaos4.11.el8 | | `ignition-validate` | Red Hat:openshift:4.11::el8 | All versions | 0:2.14.0-4.rhaos4.11.el8 | | `ignition-validate-debuginfo` | Red Hat:openshift:4.11::el8 | All versions | 0:2.14.0-4.rhaos4.11.el8 | Products: Golang Go. ## How do I fix CVE-2022-30629? Upgrade golang to a fixed version for your release line: 1.17.11 or 1.18.3. ## Is CVE-2022-30629 being exploited? There is no known exploitation of CVE-2022-30629 in the wild and no public exploit code. ## Other vulnerabilities in Golang Go - [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild) - [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8) - [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8) - [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8) - [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-30629 and fix it if it is affected. What it is: CVE-2022-30629 is a low-severity vulnerability in Golang Go, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-30629 in the wild and no public exploit code. Affected packages and fixed versions: - golang (Bitnami): affected all versions; fixed in 1.17.11, 1.18.3 - stdlib (Go): affected all versions; fixed in 1.17.11, 1.18.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-30629/ (Markdown: https://insights.sbomify.com/CVE-2022-30629/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30629 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30629 - OSV: https://osv.dev/vulnerability/CVE-2022-30629 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-30629/ Summaries are generated and may contain mistakes; the official description above is the record.