Skip to content
Fencer Intel
medium 5.3

CVE-2022-0613 json

Authorization Bypass Through User-Controlled Key in medialize/uri.js

published 4y ago modified 4mo ago also GHSA-gcv8-gh4r-25x6 , EUVD-2022-1011

cvss
5.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

Authorization Bypass Through User-Controlled Key in NPM urijs prior to 1.19.8.

Patch / fix

  • npm urijs 1.19.8
  • medialize medialize/uri.js 1.19.8
  • rh-dotnet31-dotnet RHEL 3.1 DOTNET 3.1.418-1.el7_9
  • rh-dotnet31-dotnet-host RHEL 3.1 DOTNET 3.1.24-1.el7_9
  • rh-dotnet31-dotnet-sdk-3.1 RHEL 3.1 DOTNET 3.1.418-1.el7_9
  • rh-dotnet31-dotnet-hostfxr-3.1 RHEL 3.1 DOTNET 3.1.24-1.el7_9
  • rh-dotnet31-dotnet-runtime-3.1 RHEL 3.1 DOTNET 3.1.24-1.el7_9
  • rh-dotnet31-dotnet-templates-3.1 RHEL 3.1 DOTNET 3.1.418-1.el7_9
  • rh-dotnet31-aspnetcore-runtime-3.1 RHEL 3.1 DOTNET 3.1.24-1.el7_9
  • rh-dotnet31-dotnet-apphost-pack-3.1 RHEL 3.1 DOTNET 3.1.24-1.el7_9

red hat advisories RHBA-2022:1352RHBA-2022:1386

Is CVE-2022-0613 in your dependencies? 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-0613 updated cvss 6.5

urijs: Authorization Bypass Through User-Controlled Key

  • Red Hat .NET Core 5.0 on Red Hat Enterprise Linux rh-dotnet50-dotnet, rh-dotnet50-dotnet-host, rh-dotnet50-dotnet-sdk-5.0, rh-dotnet50-dotnet-hostfxr-5.0, rh-dotnet50-dotnet-runtime-5.0, rh-dotnet50-dotnet-templates-5.0, +6 more
    affected: no fix planned “Out of support scope”
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/mcm-topology-rhel8, rhacm2/application-ui-rhel8
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat Enterprise Linux 8 dotnet, dotnet5.0, dotnet-host, dotnet-sdk-5.0, dotnet-hostfxr-5.0, dotnet-runtime-5.0, +7 more
    affected: no fix planned “Will not fix”
  • Red Hat Quay 3 quay/quay-rhel8
    affected: no fix available
  • Red Hat .NET Core on Red Hat Enterprise Linux ComputeNode (v. 7) rh-dotnet31-dotnet 3.1.418-1.el7_9, rh-dotnet31-dotnet-host 3.1.24-1.el7_9, rh-dotnet31-dotnet-sdk-3.1 3.1.418-1.el7_9, rh-dotnet31-dotnet-hostfxr-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-runtime-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-templates-3.1 3.1.418-1.el7_9, +6 more Red Hat .NET Core on Red Hat Enterprise Linux Server (v. 7) rh-dotnet31-dotnet 3.1.418-1.el7_9, rh-dotnet31-dotnet-host 3.1.24-1.el7_9, rh-dotnet31-dotnet-sdk-3.1 3.1.418-1.el7_9, rh-dotnet31-dotnet-hostfxr-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-runtime-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-templates-3.1 3.1.418-1.el7_9, +6 more Red Hat .NET Core on Red Hat Enterprise Linux Workstation (v. 7) rh-dotnet31-dotnet 3.1.418-1.el7_9, rh-dotnet31-dotnet-host 3.1.24-1.el7_9, rh-dotnet31-dotnet-sdk-3.1 3.1.418-1.el7_9, rh-dotnet31-dotnet-hostfxr-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-runtime-3.1 3.1.24-1.el7_9, rh-dotnet31-dotnet-templates-3.1 3.1.418-1.el7_9, +6 more
    fixed: vendor fix RHBA-2022:1352
  • Red Hat CodeReady Linux Builder (v. 8) dotnet-sdk-3.1-source-built-artifacts 3.1.418-1.el8_5 Red Hat Enterprise Linux AppStream (v. 8) dotnet3.1 3.1.418-1.el8_5, dotnet-sdk-3.1 3.1.418-1.el8_5, dotnet-hostfxr-3.1 3.1.24-1.el8_5, dotnet-runtime-3.1 3.1.24-1.el8_5, dotnet-templates-3.1 3.1.418-1.el8_5, aspnetcore-runtime-3.1 3.1.24-1.el8_5, +3 more
    fixed: vendor fix RHBA-2022:1386
  • Red Hat Fuse 7.11.1
    fixed: vendor fix RHSA-2022:8652

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

1.54% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/f53d5c42-c108-40b8-917d-9dad51535083 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm urijs
<1.19.8
1.19.8

Affected products

  • medialize medialize/uri.js

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

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.