Skip to content
Fencer Intel
medium 6.1

CVE-2020-8823 json

Cross-site scripting in SocksJS-node

published 6y ago modified last mo. also GHSA-hh8v-jmh3-9437 , EUVD-2021-0832

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

htmlfile in lib/transport/htmlfile.js in SockJS before 0.3.0 is vulnerable to Reflected XSS via the /htmlfile c (aka callback) parameter.

Patch / fix

  • npm sockjs 0.3.0
  • sockjs_project sockjs 0.3.0

Is CVE-2020-8823 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-2020-8823 updated cvss 6.1

sockJS: function htmlfile is not checking the non-alphanumeric symbols which could result in reflected XSS

  • Red Hat Distributed Tracing Jaeger 1 jaeger Red Hat OpenShift Service Mesh 1 kiali, jaeger, servicemesh-grafana, servicemesh-grafana-prometheus Red Hat OpenShift Application Runtimes vertx-sockjs-service-proxy vertx-sockjs-service-proxy
    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

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

Exploits and checks

  • github.com https://github.com/theyiyibest/Reflected-XSS-on-SockJS referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm sockjs
<0.3.0
0.3.0

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.