Skip to content
Fencer Vulns
low 2.6

CVE-2021-4294 json

OpenShift OSIN CheckClientSecret timing discrepancy

published 2022-12-28 3 y ago modified 2026-06-17 4 mo ago also GHSA-m7qp-cj9p-gj85 , GO-2022-1201 , EUVD-2022-7680

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

A vulnerability was found in OpenShift OSIN. It has been classified as problematic. This affects the function ClientSecretMatches/CheckClientSecret. The manipulation of the argument secret leads to observable timing discrepancy. The name of the patch is 8612686d6dda34ae9ef6b5a974e4b7accb4fea29. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216987.

Patch / fix

  • go github.com/openshift/osin 1.0.2-0.20210113124101-8612686d6dda

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-2021-4294 updated cvss 5.9

osin: manipulation of the argument secret leads to observable timing discrepancy

  • Red Hat OpenShift Container Platform 4.12 openshift4/ose-oauth-server-rhel8 v4.12.0-202405091536.p0.g0c434f4.assembly.stream.el8
    fixed: vendor fix RHSA-2024:2782
  • Red Hat OpenShift Container Platform 4.13 openshift4/ose-oauth-server-rhel8 v4.13.0-202404200313.p0.geb54be2.assembly.stream.el8
    fixed: vendor fix RHSA-2024:2047
  • Red Hat OpenShift Container Platform 4.14 openshift4/ose-oauth-server-rhel8 v4.14.0-202310201027.p0.g37df9ff.assembly.stream
    fixed: vendor fix RHSA-2023:5006
  • Red Hat OpenShift Container Platform 4.12 rhcos 412.86.202405092134-0, openshift4/ose-cli v4.12.0-202405091536.p0.gd691257.assembly.stream.el8, openshift4/ose-pod v4.12.0-202405091536.p0.g054f0ba.assembly.stream.el8, openshift4/ose-etcd v4.12.0-202405091536.p0.gbb82e89.assembly.stream.el8, openshift4/ose-tests v4.12.0-202405091536.p0.g7b7d4ef.assembly.stream.el8, openshift4/ose-console v4.12.0-202405091536.p0.g5d4bea1.assembly.stream.el8, +185 more Red Hat OpenShift Container Platform 4.13 rhcos 413.92.202404232117-0, openshift4/ose-cli v4.13.0-202404200313.p0.gd192e90.assembly.stream.el8, openshift4/ose-pod v4.13.0-202404222237.p0.g4818370.assembly.stream.el8, openshift4/ose-tests v4.13.0-202404231936.p0.g99b9d53.assembly.stream.el8, openshift4/ose-console v4.13.0-202404231936.p0.ga1d0be0.assembly.stream.el8, openshift4/ose-coredns v4.13.0-202404200313.p0.g298d919.assembly.stream.el8, +184 more Red Hat OpenShift Container Platform 4.14 rhcos 414.92.202310210434-0, openshift4/ose-cli v4.14.0-202310201027.p0.g0c63f9d.assembly.stream, openshift4/ose-pod v4.14.0-202310210404.p0.gf67aeb3.assembly.stream, openshift4/ose-tests v4.14.0-202310201027.p0.g948001a.assembly.stream, openshift4/ose-console v4.14.0-202310201027.p0.gc16ab01.assembly.stream, openshift4/ose-coredns v4.14.0-202310201027.p0.gfd70cf1.assembly.stream, +180 more
    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

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA 3.0 2.6 CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openshift/osin
<1.0.2-0.20210113124101-8612686d6dda
1.0.2-0.20210113124101-8612686d6dda

Affected products

  • OpenShift OSIN

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy
  • CWE-203 Observable Discrepancy

References

Sources

Fencer Vulns 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.