Skip to content
Fencer Intel
medium 6.5

CVE-2013-3993 kev+ ransomware in the critical feed json

IBM InfoSphere BigInsights before 2.1.0.3 allows remote authenticated users to bypass intended file and directory restrictions, or access u…

published 12y ago modified 2mo ago also EUVD-2013-3925

cvss
6.5
version 3.1, CNA
cisa kev
Exploited
added 2022-05-25, used in ransomware
epss
4.8%
EPSS 4.8% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

IBM InfoSphere BigInsights before 2.1.0.3 allows remote authenticated users to bypass intended file and directory restrictions, or access untrusted data or code, via crafted parameters in unspecified API calls.

Patch / fix

cisa required action The impacted product is end-of-life and should be disconnected if still in use.

  • ibm infosphere_biginsights 2.1.0.3

Is CVE-2013-3993 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

Timeline

  1. Published
  2. Added to CISA KEV
  3. CISA patch deadline
  4. CISA SSVC: exploitation active

Known exploited

Added
4y ago
Patch by
2022-06-15 (4y ago)
Ransomware
Known to be used in ransomware campaigns
Required action
The impacted product is end-of-life and should be disconnected if still in use.
Vendor, product
IBM, InfoSphere BigInsights
CISA name
IBM InfoSphere BigInsights Invalid Input Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.