CyberSecBulletin
CVE-2013-3993Exploited in the wildNVD status: Analyzed

IBM InfoSphere BigInsights Invalid Input

CVE-2013-3993 is a low-severity improper limitation of a pathname to a restricted directory vulnerability in Infosphere Biginsights from IBM, with a CVSS 2.0 base score of 3.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.1.0.3 as the first without the flaw, so updating Infosphere Biginsights to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on May 25, 2022, which means attacks have been observed in the wild, including in ransomware campaigns.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Infosphere Biginsights to 2.1.0.3 or a later version.
  2. CISA's required action: The impacted product is end-of-life and should be disconnected if still in use.
  3. Read the advisory on www-01.ibm.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
IBMInfosphere Biginsightsbefore 2.1.0.32.1.0.3

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Access vector
NetworkCan be exploited remotely over a network.
Access complexity
MediumSome conditions must be met.
Authentication
SingleOne login is needed.
Confidentiality
PartialSome data can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: AV:N/AC:M/Au:S/C:P/I:N/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.5MediumCISA (ADP)
CVSS 2.03.5LowNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.