Vulnerabilities

5 via 10 paths

Dependencies

638

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 3
  • 1
Status
  • 5
  • 0
  • 0

critical severity

Embedded Malicious Code

  • Vulnerable module: size-sensor
  • Introduced through: echarts-for-react@3.0.6

Detailed paths

  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › echarts-for-react@3.0.6 › size-sensor@1.0.4

Overview

Affected versions of this package are vulnerable to Embedded Malicious Code that conceals a credential-stealing payload and worm propagation logic. A malicious actor associated with the "TeamPCP" or "Mini Shai-Hulud" campaign compromised a maintainer's access token; this allowed the attacker to publish over 600 tampered package versions to npm, primarily targeting the @antv ecosystem, along with other widely used packages like echarts-for-react, size-sensor, and jest-canvas-mock.

Attack Details

This supply chain attack is notable for successfully forging valid Sigstore provenance badges, meaning the malicious packages appear legitimate to standard provenance-verification tools. The attackers introduced the malware using a "phantom commit dropper," injecting an anomalous @antv/setup optional dependency that points directly to a malicious GitHub commit.

Malware Behavior

The heavily obfuscated payload is designed to execute during the package installation phase. It scans developer workstations and CI/CD pipelines to harvest high-value secrets, including AWS credentials, GitHub tokens, npm tokens, Vault tokens, and Kubernetes service-account material. The stolen data is compressed, encrypted, and exfiltrated to an external server. If the primary exfiltration route fails, the malware falls back on abusing stolen GitHub tokens to create Dune-themed repositories under the victim's account to stash the stolen data. The payload also contains worm capabilities, using stolen npm tokens to modify and republish further packages.

Remediation

Avoid using all malicious instances of the size-sensor package.

References

high severity
new

Uncontrolled Recursion

  • Vulnerable module: braces
  • Introduced through: ts-checker-rspack-plugin@1.6.2

Detailed paths

  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › ts-checker-rspack-plugin@1.6.2 › chokidar@3.6.0 › braces@3.0.3

Overview

braces is a Bash-like brace expansion, implemented in JavaScript.

Affected versions of this package are vulnerable to Uncontrolled Recursion in the recursive AST walkers, which lack depth guards. An attacker can supply deeply nested brace patterns that stay within the character limit to exhaust the call stack and crash the Node.js process with an uncaught RangeError.

Remediation

There is no fixed version for braces.

References

high severity
new

Inefficient Algorithmic Complexity

  • Vulnerable module: postcss-selector-parser
  • Introduced through: rehype-expressive-code@0.44.2

Detailed paths

  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › rehype-expressive-code@0.44.2 › expressive-code@0.44.2 › @expressive-code/core@0.44.2 › postcss-nested@6.2.0 › postcss-selector-parser@6.1.4
  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › rehype-expressive-code@0.44.2 › expressive-code@0.44.2 › @expressive-code/plugin-frames@0.44.2 › @expressive-code/core@0.44.2 › postcss-nested@6.2.0 › postcss-selector-parser@6.1.4
  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › rehype-expressive-code@0.44.2 › expressive-code@0.44.2 › @expressive-code/plugin-shiki@0.44.2 › @expressive-code/core@0.44.2 › postcss-nested@6.2.0 › postcss-selector-parser@6.1.4
  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › rehype-expressive-code@0.44.2 › expressive-code@0.44.2 › @expressive-code/plugin-text-markers@0.44.2 › @expressive-code/core@0.44.2 › postcss-nested@6.2.0 › postcss-selector-parser@6.1.4

Overview

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the uniqs helper and index-membership checks in src/parser.js when parsing flat selectors (e.g. .a.a.a...) containing a large number of class or ID tokens. The original implementation uses Array.indexOf inside a filter callback and repeated linear scans of the hasClass/hasId arrays, producing quadratic time complexity proportional to the number of tokens. An attacker who can supply selector input to the parser can trigger CPU exhaustion by providing a long flat selector, pinning a CPU core and causing the process to become unresponsive.

Remediation

Upgrade postcss-selector-parser to version 7.1.6 or higher.

References

high severity

Open Redirect

  • Vulnerable module: react-router
  • Introduced through: react-router@6.30.6 and react-router-dom@6.30.6

Detailed paths

  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › react-router@6.30.6
    Remediation: Upgrade to react-router@7.18.0.
  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › react-router-dom@6.30.6 › react-router@6.30.6
    Remediation: Upgrade to react-router-dom@7.18.0.

Overview

Affected versions of this package are vulnerable to Open Redirect via the navigation mechanisms when attacker-supplied paths containing a backslash are processed. An attacker can redirect users to unintended external sites by crafting malicious links or inputs.

Remediation

Upgrade react-router to version 7.18.0 or higher.

References

medium severity

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

  • Vulnerable module: react-router
  • Introduced through: react-router@6.30.6 and react-router-dom@6.30.6

Detailed paths

  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › react-router@6.30.6
    Remediation: Upgrade to react-router@7.18.0.
  • Introduced through: @sentry-internal/monorepo@getsentry/sentry › react-router-dom@6.30.6 › react-router@6.30.6
    Remediation: Upgrade to react-router-dom@7.18.0.

Overview

Affected versions of this package are vulnerable to Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') in the deserializeErrors function during SSR hydration. An attacker can cause unexpected constructor execution on the client, potentially resulting in outbound network traffic, by supplying crafted input that overwrites certain aspects of errors caught by the SSR process.

Note: This is only exploitable if the application is running in Framework Mode or Data Mode and performs manual SSR/hydration with code that allows attacker-controlled input to influence error deserialization.

Remediation

Upgrade react-router to version 7.18.0 or higher.

References