Skip to content

Commit 43149b5

Browse files
jasnowpostmodern
authored andcommitted
GHSA SYNC: 1 brand new advisory
1 parent f4e7641 commit 43149b5

File tree

1 file changed

+46
-0
lines changed

1 file changed

+46
-0
lines changed

gems/jwe/CVE-2025-54887.yml

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
gem: jwe
3+
cve: 2025-54887
4+
ghsa: c7p4-hx26-pr73
5+
url: https://github.com/jwt/ruby-jwe/security/advisories/GHSA-c7p4-hx26-pr73
6+
title: JWE is missing AES-GCM authentication tag validation in encrypted JWE
7+
date: 2025-08-07
8+
description: |
9+
### Overview
10+
11+
The authentication tag of encrypted JWEs can be brute forced,
12+
which may result in loss of confidentiality for those JWEs and
13+
provide ways to craft arbitrary JWEs.
14+
15+
### Impact
16+
17+
- JWEs can be modified to decrypt to an arbitrary value
18+
- JWEs can be decrypted by observing parsing differences
19+
- The GCM internal
20+
[GHASH key](https://en.wikipedia.org/wiki/Galois/Counter_Mode)
21+
can be recovered
22+
23+
### Am I Affected?
24+
25+
You are affected by this vulnerability even if you do not
26+
use an `AES-GCM` encryption algorithm for your JWEs.
27+
28+
### Patches
29+
30+
The version 1.1.1 fixes the issue by adding the tag length check for the `AES-GCM` algorithm.
31+
32+
**Important:** As the [GHASH key](https://en.wikipedia.org/wiki/Galois/Counter_Mode)
33+
could have leaked, you must rotate the encryption keys after
34+
upgrading to version 1.1.1.
35+
36+
### References
37+
38+
[Félix Charette talk at NorthSec 2025 about the issue](https://www.youtube.com/watch?v=9IT659uUXfs&t=15830s)
39+
cvss_v3: 9.1
40+
patched_versions:
41+
- ">= 1.1.1"
42+
related:
43+
url:
44+
- https://github.com/jwt/ruby-jwe/security/advisories/GHSA-c7p4-hx26-pr73
45+
- https://github.com/jwt/ruby-jwe/releases/tag/v1.1.1
46+
- https://github.com/advisories/GHSA-c7p4-hx26-pr73

0 commit comments

Comments
 (0)