Skip to content

Commit b8487a2

Browse files
committed
0.17.12.
1 parent ef8bac6 commit b8487a2

File tree

2 files changed

+16
-2
lines changed

2 files changed

+16
-2
lines changed

Cargo.toml

+2-2
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,14 @@ repository = "https://github.com/ctz/ring"
1313
rust-version = "1.63.0"
1414

1515
# Keep in sync with `links` below.
16-
version = "0.17.11"
16+
version = "0.17.12"
1717

1818
# Keep in sync with `version` above.
1919
#
2020
# build.rs verifies that this equals "ring_core_{major}_{minor}_{patch}_{pre}"
2121
# as keeping this in sync with the symbol prefixing is crucial for ensuring
2222
# the safety of multiple versions of *ring* being used in a program.
23-
links = "ring_core_0_17_11_"
23+
links = "ring_core_0_17_12_"
2424

2525
include = [
2626
"LICENSE",

RELEASES.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
Version 0.17.12 (2025-03-05)
2+
============================
3+
Bug fix: https://github.com/briansmith/ring/pull/2447 for denial of service (DoS).
4+
5+
Fixes a panic in `ring::aead::quic::HeaderProtectionKey::new_mask()` when
6+
integer overflow checking is enabled. Integer overflow checking is not enabled
7+
in release mode by default, but `RUSTFLAGS="-C overflow-checks"` or
8+
`overflow-checks = true` in the Cargo.toml profile can override this.
9+
10+
This panic could also be hit when using `ring::aead::aes_gcm` when
11+
encrypting/decrypting approximately 68,719,476,700 bytes (about 64 gigabytes)
12+
of data using AES-GCM in a single packet. Networking protocols, like SSH and
13+
TLS, can't be affected by this because they break data sent/received into much,
14+
much smaller packet sizes.

0 commit comments

Comments
 (0)