Vulnerabilities

2 via 20 paths

Dependencies

304

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 2
Status
  • 2
  • 0
  • 0

high severity

Uncontrolled Recursion

  • Vulnerable module: ioredis
  • Introduced through: probot@13.4.7

Detailed paths

  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › ioredis@5.11.1
    Remediation: Upgrade to probot@14.0.0.

Overview

ioredis is a Redis client for Node.js.

Affected versions of this package are vulnerable to Uncontrolled Recursion in the RESP protocol parser in lib/parser.js. An attacker can crash the Node.js client process by sending crafted RESP byte streams with repeated nested array headers. The parser recurses while handling nested arrays, exhausting the V8 call stack and triggering an uncaught RangeError. In affected deployments that consume data from a malicious or compromised Redis endpoint, this terminates the process and disrupts Redis client operations.

Remediation

Upgrade ioredis to version 6.0.0-beta.1 or higher.

References

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: @opentelemetry/core
  • Introduced through: probot@13.4.7

Detailed paths

  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-amqplib@0.46.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-connect@0.43.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-express@0.47.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-fastify@0.44.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-fs@0.19.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-hapi@0.45.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-http@0.57.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-koa@0.47.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-mongoose@0.46.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-pg@0.50.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-undici@0.10.0 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/resources@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-mysql2@0.45.0 › @opentelemetry/sql-common@0.40.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/instrumentation-pg@0.50.0 › @opentelemetry/sql-common@0.40.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/resources@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @prisma/instrumentation@5.22.0 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.
  • Introduced through: darkest-PR@skywarth/darkest-PR › probot@13.4.7 › @probot/pino@3.0.0 › @sentry/node@8.55.2 › @prisma/instrumentation@5.22.0 › @opentelemetry/sdk-trace-base@1.30.1 › @opentelemetry/resources@1.30.1 › @opentelemetry/core@1.30.1
    Remediation: Upgrade to probot@14.0.0.

Overview

@opentelemetry/core is an OpenTelemetry Core provides constants and utilities shared by all OpenTelemetry SDK packages.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the extract function. An attacker can cause excessive memory allocation by sending oversized baggage HTTP headers or equivalent data via non-HTTP transports.

Note: This is only exploitable if the deployment does not enforce transport-layer header size limits, such as when using custom transports or when default HTTP header size limits are increased.

Workaround

This vulnerability can be mitigated by configuring strict header size limits at the server or gateway level, or by validating input size before passing it to the propagator in non-HTTP transports.

Remediation

Upgrade @opentelemetry/core to version 2.8.0 or higher.

References