Skip to content
Fencer Vulns
high 8.1

CVE-2016-10621 json

Downloads Resources over HTTP in fibjs

published 2018-06-01 8 y ago modified 2026-06-17 4 mo ago also GHSA-6p48-xfj3-jw67 , EUVD-2019-0243

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

fibjs is a runtime for javascript applictions built on google v8 JS. fibjs downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.

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-2016-10621 updated cvss 7.4

v8: fibjs runtime downloads binary resources over HTTP

  • Red Hat Subscription Asset Manager v8
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) v8 Red Hat OpenStack Platform 8 (Liberty) v8 Red Hat OpenStack Platform 9 (Mitaka) v8 Red Hat OpenStack Platform 10 (Newton) v8 Red Hat Satellite 6 v8
    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.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected packages

ecosystem package affected fixed in
npm fibjs
<=0.1.8
 no fix listed

Affected products

  • HackerOne fibjs node module

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-310 Cryptographic Issues

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.