Skip to content
Fencer Intel
no cvss —

CVE-2022-23529 json

DO NOT USE THIS CANDIDATE NUMBER.

published 3y ago modified last yr.

Withdrawn or rejected on

Its source no longer considers this a valid vulnerability. It stays here so links keep working, and it is left out of feeds.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The issue is not a vulnerability. Notes: none.

Is CVE-2022-23529 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-23529 updated cvss 0.0

jsonwebtoken: Insecure input validation in jwt.verify function

  • Red Hat OpenShift Container Platform 4 openshift4/ose-console Red Hat Openshift Container Storage 4 ocs4/mcg-core-rhel8 Red Hat Openshift Data Foundation 4 odf4/mcg-core-rhel9, noobaa-core-container
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.