Skip to content

chore(deps): update jsonwebtoken to 10.3.0#44

Merged
kevinzs2048 merged 5 commits into
veraison:mainfrom
Xynnn007:chore-jsonwebtoken
Mar 30, 2026
Merged

chore(deps): update jsonwebtoken to 10.3.0#44
kevinzs2048 merged 5 commits into
veraison:mainfrom
Xynnn007:chore-jsonwebtoken

Conversation

@Xynnn007
Copy link
Copy Markdown
Collaborator

This will help resolve the vulunaribility of

  • jsonwebtoken has Type Confusion that leads to potential authorization bypass

Hi @thomas-fossati Could you help to get this in and publish a new release if it looks good to you? We downstream found the vulnerable.

This will help resolve the vulunaribility of

- jsonwebtoken has Type Confusion that leads to potential authorization bypass

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
@Xynnn007 Xynnn007 marked this pull request as draft March 24, 2026 03:58
@Xynnn007 Xynnn007 marked this pull request as ready for review March 24, 2026 04:48
@Xynnn007
Copy link
Copy Markdown
Collaborator Author

Looks like the CI errors are not related to this PR.

This is to fix the lint error like
```
warning: struct `Bytes` is never constructed
  --> src/token/base64.rs:20:12
   |
20 | pub struct Bytes(Vec<u8>);
   |            ^^^^^
   |
   = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
```

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
fix error like

```
error: called `unwrap` on `v.realm` after checking its variant with `is_some`
  --> src/store/memo_refvaluestore.rs:44:21
   |
43 |         if v.realm.is_some() {
   |         -------------------- help: try: `if let Some(<item>) = &v.realm`
44 |             let p = v.realm.as_ref().unwrap();
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#unnecessary_unwrap
```

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
The bitmask crate has not been actively maintained for a long time, and
new version of cargo suites will raise lint error of the logic inside
that crate. We use a actively maintained crate bitflags to replace
bitmask to fix the errors like

```
warning: unexpected `cfg` condition value: `std`
  --> src/token/platform.rs:17:1
   |
17 | / bitmask! {
18 | |     #[derive(Debug)]
19 | |     mask SwClaimsSet: u8 where flags SwClaims {
20 | |         MTyp     = 0x01,
...  |
27 | | }
   | |_^
   |
   = note: no expected values for `feature`
   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
   = help: try referring to `bitmask` crate for guidance on how handle this unexpected cfg
   = help: the macro `bitmask` may come from an old version of the `bitmask` crate, try updating your dependency with `cargo update -p bitmask`
   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
   = note: `#[warn(unexpected_cfgs)]` on by default
   = note: this warning originates in the macro `bitmask` (in Nightly builds, run with -Z macro-backtrace for more info)
```

Signed-off-by: Xynnn007 <xynnn@linux.alibaba.com>
@Xynnn007
Copy link
Copy Markdown
Collaborator Author

let me help to resolve the lint errors.

@Xynnn007
Copy link
Copy Markdown
Collaborator Author

Xynnn007 commented Mar 24, 2026

well. I do not know why the cargo-deny blocks, but looks like not related to the PR again. I am not planning to resolve that in this PR because I am not familiar with this part ; )

This also updates openssl from v0.10.34 to v0.10.72 to addres CVE-2025-3416

Signed-off-by: Thomas Fossati <thomas.fossati@linaro.org>
Copy link
Copy Markdown
Contributor

@thomas-fossati thomas-fossati left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@kevinzs2048 kevinzs2048 merged commit a3080f1 into veraison:main Mar 30, 2026
4 checks passed
@Xynnn007 Xynnn007 deleted the chore-jsonwebtoken branch March 30, 2026 03:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants