search

2lambda123 / CycloneDX-cyclonedx-webpack-plugin

Apache License 2.0
0 stars 0 forks source link

chore(deps): bump the npm_and_yarn group across 2 directories with 4 updates #11

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the npm_and_yarn group with 3 updates in the /tests/integration/webpack5-angular13 directory: ws, engine.io and socket.io-adapter. Bumps the npm_and_yarn group with 2 updates in the /tests/integration/webpack5-react18 directory: postcss and ws.

Updates ws from 8.17.0 to 8.17.1

Release notes

Sourced from ws's releases.

8.17.1

Bug fixes

  • Fixed a DoS vulnerability (#2231).

A request with a number of headers exceeding the[server.maxHeadersCount][] threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;


for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;


for (let j = 0; j &lt; chars.length; j++) {
  const key = chars[i] + chars[j];
  headers[key] = 'x';

  if (++count === 2000) break;
}



}


headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';


const request = http.request({
headers: headers,
host: '127.0.0.1',
port: wss.address().port
});


request.end();
});

The vulnerability was reported by Ryan LaPointe in websockets/ws#2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

  1. Reduce the maximum allowed length of the request headers using the [--max-http-header-size=size][] and/or the [maxHeaderSize][] options so that no more headers than the server.maxHeadersCount limit can be sent.

... (truncated)

Commits
  • 3c56601 [dist] 8.17.1
  • e55e510 [security] Fix crash when the Upgrade header cannot be read (#2231)
  • 6a00029 [test] Increase code coverage
  • ddfe4a8 [perf] Reduce the amount of crypto.randomFillSync() calls
  • See full diff in compare view


Updates engine.io from 6.5.2 to 6.5.5

Release notes

Sourced from engine.io's releases.

6.5.5

This release contains a bump of the ws dependency, which includes an important security fix.

Advisory: https://github.com/advisories/GHSA-3h5v-q93c-6h6q

Bug Fixes

Links

6.5.4

This release contains some minor changes which should improve the memory usage of the server, notably this.

Links

6.5.3

Bug Fixes

  • improve compatibility with node16 module resolution (#689) (c6bf8c0)
  • webtransport: properly handle abruptly closed connections (ff1c861)

Links

Changelog

Sourced from engine.io's changelog.

6.5.5 (2024-06-18)

This release contains a bump of the ws dependency, which includes an important security fix.

Advisory: https://github.com/advisories/GHSA-3h5v-q93c-6h6q

Bug Fixes

Dependencies

3.6.2 (2024-06-18)

This release contains a bump of the ws dependency, which includes an important security fix.

Advisory: https://github.com/advisories/GHSA-3h5v-q93c-6h6q

Dependencies

6.5.4 (2023-11-09)

This release contains some minor changes which should improve the memory usage of the server, notably this.

Dependencies

6.5.3 (2023-10-06)

Bug Fixes

  • improve compatibility with node16 module resolution (#689) (c6bf8c0)
  • webtransport: properly handle abruptly closed connections (ff1c861)

Dependencies

... (truncated)

Commits


Updates socket.io-adapter from 2.5.2 to 2.5.5

Release notes

Sourced from socket.io-adapter's releases.

2.5.4

Bug Fixes

  • ensure the order of the commands (a13f35f)
  • types: ensure compatibility with TypeScript < 4.5 (ca397f3)

Links

2.5.3

Two abstract classes were imported from the Redis adapter repository:

  • the ClusterAdapter class, which manages the messages sent between the server instances of the cluster
  • the ClusterAdapterWithHeartbeat class, which extends the ClusterAdapter and adds a heartbeat mechanism in order to check the healthiness of the other instances

Other adapters can then just extend those classes and only have to implement the pub/sub mechanism (and not the internal chit-chat protocol):

class MyAdapter extends ClusterAdapterWithHeartbeat {
  constructor(nsp, pubSub, opts) {
    super(nsp, opts);
    this.pubSub = pubSub;
    pubSub.subscribe("main-channel", (message) => this.onMessage(message));
    pubSub.subscribe("specific-channel#" + this.uid, (response) => this.onResponse(response));
  }

doPublish(message) {
return this.pubSub.publish("main-channel", message);
}


doPublishResponse(requesterUid, response) {
return this.pubSub.publish("specific-channel#" + requesterUid, response);
}
}

Besides, the number of "timeout reached: only x responses received out of y" errors (which can happen when a server instance leaves the cluster) should be greatly reduced by this commit.

Bug Fixes

  • cluster: fix count in fetchSockets() method (80af4e9)
  • cluster: notify the other nodes when closing (0e23ff0)

Performance Improvements

  • cluster: use timer.refresh() (d99a71b)

... (truncated)

Changelog

Sourced from socket.io-adapter's changelog.

2.5.5 (2024-06-18)

This release contains a bump of the ws dependency, which includes an important security fix.

Advisory: https://github.com/advisories/GHSA-3h5v-q93c-6h6q

2.5.4 (2024-02-22)

Bug Fixes

  • ensure the order of the commands (a13f35f)
  • types: ensure compatibility with TypeScript < 4.5 (ca397f3)

2.5.3 (2024-02-21)

Two abstract classes were imported from the Redis adapter repository:

  • the ClusterAdapter class, which manages the messages sent between the server instances of the cluster
  • the ClusterAdapterWithHeartbeat class, which extends the ClusterAdapter and adds a heartbeat mechanism in order to check the healthiness of the other instances

Other adapters can then just extend those classes and only have to implement the pub/sub mechanism (and not the internal chit-chat protocol):

class MyAdapter extends ClusterAdapterWithHeartbeat {
  constructor(nsp, pubSub, opts) {
    super(nsp, opts);
    this.pubSub = pubSub;
    pubSub.subscribe("main-channel", (message) => this.onMessage(message));
    pubSub.subscribe("specific-channel#" + this.uid, (response) => this.onResponse(response));
  }

doPublish(message) {
return this.pubSub.publish("main-channel", message);
}


doPublishResponse(requesterUid, response) {
return this.pubSub.publish("specific-channel#" + requesterUid, response);
}
}

Besides, the number of "timeout reached: only x responses received out of y" errors (which can happen when a server instance leaves the cluster) should be greatly reduced by this commit.

Bug Fixes

... (truncated)

Commits
  • 05a190a chore(release): 6.5.5
  • 93fe190 chore(deps): bump ws from 8.11.0 to 8.17.1 (#93)
  • 5eae5a0 chore(release): 2.5.4
  • 005d546 ci: test with older TypeScript version
  • a13f35f fix: ensure the order of the commands
  • 207c0db refactor: break circular dependency (2)
  • abc93a9 refactor: break circular dependency (1)
  • 9d4c4a7 refactor(cluster): export ClusterAdapterOptions and MessageType types
  • ca397f3 fix(types): ensure compatibility with TypeScript < 4.5
  • 549156c chore(release): 2.5.3
  • Additional commits viewable in compare view


Updates postcss from 8.4.33 to 8.4.34

Release notes

Sourced from postcss's releases.

8.4.34

Changelog

Sourced from postcss's changelog.

8.4.34

  • Fixed AtRule#nodes type (by Tim Weißenfels).
  • Cleaned up code (by Dmitry Kirillov).
Commits


Updates ws from 7.5.9 to 7.5.10

Release notes

Sourced from ws's releases.

8.17.1

Bug fixes

  • Fixed a DoS vulnerability (#2231).

A request with a number of headers exceeding the[server.maxHeadersCount][] threshold could be used to crash a ws server.

const http = require('http');
const WebSocket = require('ws');

const wss = new WebSocket.Server({ port: 0 }, function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;


for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;


for (let j = 0; j &lt; chars.length; j++) {
  const key = chars[i] + chars[j];
  headers[key] = 'x';

  if (++count === 2000) break;
}



}


headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';


const request = http.request({
headers: headers,
host: '127.0.0.1',
port: wss.address().port
});


request.end();
});

The vulnerability was reported by Ryan LaPointe in websockets/ws#2230.

In vulnerable versions of ws, the issue can be mitigated in the following ways:

  1. Reduce the maximum allowed length of the request headers using the [--max-http-header-size=size][] and/or the [maxHeaderSize][] options so that no more headers than the server.maxHeadersCount limit can be sent.

... (truncated)

Commits
  • 3c56601 [dist] 8.17.1
  • e55e510 [security] Fix crash when the Upgrade header cannot be read (#2231)
  • 6a00029 [test] Increase code coverage
  • ddfe4a8 [perf] Reduce the amount of crypto.randomFillSync() calls
  • See full diff in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/2lambda123/CycloneDX-cyclonedx-webpack-plugin/network/alerts).
performance-testing-bot[bot] commented 4 months ago

Unable to locate .performanceTestingBot config file

cr-gpt[bot] commented 4 months ago

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

code-companion-ai[bot] commented 4 months ago

Processing PR updates...

codesyncapp[bot] commented 4 months ago

Check out the playback for this Pull Request here.

git-greetings[bot] commented 4 months ago

Thanks @dependabot[bot] for opening this PR!

For COLLABORATOR only :

coderabbitai[bot] commented 4 months ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
git-greetings[bot] commented 4 months ago
PR Details of @dependabot[bot] in CycloneDX-cyclonedx-webpack-plugin : OPEN CLOSED TOTAL
1 8 9
guardrails[bot] commented 4 months ago

:warning: We detected 3 security issues in this pull request:

Vulnerable Libraries (3)
Severity | Details :-: | :-- High | [pkg:npm/tailwindcss@3.1.3](https://github.com/2lambda123/CycloneDX-cyclonedx-webpack-plugin/blob/9044cb336d60511d4260e025c85f246e0417e512/tests/integration/webpack5-react18/package.json) (t) upgrade to: *> 3.1.3* High | [pkg:npm/css-minimizer-webpack-plugin@3.4.1](https://github.com/2lambda123/CycloneDX-cyclonedx-webpack-plugin/blob/9044cb336d60511d4260e025c85f246e0417e512/tests/integration/webpack5-react18/package.json) (t) upgrade to: *> 3.4.1* High | [pkg:npm/webpack-dev-server@4.9.2](https://github.com/2lambda123/CycloneDX-cyclonedx-webpack-plugin/blob/9044cb336d60511d4260e025c85f246e0417e512/tests/integration/webpack5-react18/package.json) (t) upgrade to: *> 4.9.2* More info on how to fix Vulnerable Libraries in [JavaScript](https://docs.guardrails.io/docs/en/vulnerabilities/javascript/using_vulnerable_libraries.html?utm_source=ghpr).

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

socket-security[bot] commented 4 months ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@apollo/client@3.7.10 environment, network Transitive: eval +19 6.75 MB apollo-bot
npm/@babel/core@7.24.5 environment, filesystem, unsafe +33 7.85 MB nicolo-ribaudo
npm/@cyclonedx-webpack-plugin-tests/example-webpack5-react18@0.0.1 None 0 0 B
npm/@pmmmwh/react-refresh-webpack-plugin@0.5.7 environment, filesystem Transitive: eval +4 1.08 MB pmmmwh
npm/@popperjs/core@2.11.8 None 0 1.46 MB fezvrasta
npm/@svgr/webpack@8.1.0 Transitive: environment, filesystem, unsafe +140 10.3 MB neoziro
npm/@testing-library/jest-dom@5.16.4 Transitive: environment, filesystem +14 1.39 MB testing-library-bot
npm/@testing-library/react@13.3.0 environment +19 9.22 MB testing-library-bot
npm/@testing-library/user-event@13.5.0 Transitive: environment +14 3.54 MB testing-library-bot
npm/babel-jest@27.5.1 environment Transitive: eval, filesystem, shell +44 5.18 MB simenb
npm/babel-loader@8.2.5 filesystem +1 119 kB nicolo-ribaudo
npm/babel-plugin-named-asset-import@0.3.8 None 0 4.47 kB iansu
npm/babel-preset-react-app@10.0.1 environment Transitive: filesystem, unsafe +146 11.7 MB iansu
npm/bfj@7.0.2 filesystem Transitive: environment, eval, unsafe +2 1.08 MB philbooth
npm/blueimp-gallery@3.4.0 None 0 315 kB blueimp
npm/bootstrap@5.3.3 None 0 9.67 MB xhmikosr
npm/camelcase@6.3.0 None 0 11.7 kB sindresorhus
npm/case-sensitive-paths-webpack-plugin@2.4.0 None 0 25.9 kB urthen
npm/css-loader@6.7.1 None 0 129 kB evilebottnawi
npm/css-minimizer-webpack-plugin@3.4.1 eval Transitive: environment +9 1.55 MB evilebottnawi
npm/dotenv-expand@5.1.0 None 0 15.9 kB motdotla
npm/dotenv@10.0.0 environment, filesystem 0 24.9 kB motdotla
npm/html-inline-script-webpack-plugin@3.0.0 None 0 21.7 kB icelam
npm/html-webpack-plugin@5.5.0 filesystem, unsafe Transitive: environment, eval, network, shell +43 7.39 MB jantimon
npm/react@18.2.0 environment +2 337 kB gnoff
npm/vue@2.6.14 environment 0 2.97 MB posva
npm/webpack-cli@5.1.4 environment, filesystem, unsafe Transitive: eval, shell +49 1.57 MB evilebottnawi
npm/webpack@5.76.1 environment, filesystem, network, unsafe Transitive: eval, shell +75 16.1 MB evilebottnawi
npm/webpack@5.76.3 environment, filesystem, network, unsafe Transitive: eval, shell +18 13.6 MB thelarkinn
npm/webpack@5.92.0 environment, filesystem, network, unsafe Transitive: eval, shell +46 14.4 MB evilebottnawi

🚮 Removed packages: npm/@angular-builders/custom-webpack@17.0.2, npm/@angular-devkit/build-angular@17.3.7, npm/@angular/animations@13.3.12, npm/@angular/cli@17.3.7, npm/@angular/common@13.3.12, npm/@angular/compiler-cli@13.3.12, npm/@angular/compiler@13.3.12, npm/@angular/core@13.3.12, npm/@angular/forms@13.3.12, npm/@angular/platform-browser-dynamic@13.3.12, npm/@angular/platform-browser@13.3.12, npm/@angular/router@13.3.12, npm/@types/jasmine@3.10.12, npm/@types/node@12.20.55, npm/jasmine-core@4.0.1, npm/karma-chrome-launcher@3.1.1, npm/karma-coverage@2.1.1, npm/karma-jasmine-html-reporter@1.7.0, npm/karma-jasmine@4.0.2, npm/karma@6.3.20, npm/rxjs@7.5.7, npm/tslib@2.6.2, npm/typescript@4.6.4, npm/webpack@5.90.3

View full report↗︎

secure-code-warrior-for-github[bot] commented 4 months ago

Micro-Learning Topic: Vulnerable library (Detected by phrase)

Matched on "Vulnerable Libraries"

What is this? (2min video)

Use of vulnerable components will introduce weaknesses into the application. Components with published vulnerabilities will allow easy exploitation as resources will often be available to automate the process.

Try a challenge in Secure Code Warrior

socket-security[bot] commented 4 months ago

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Install scripts npm/core-js-pure@3.23.1
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
 🚫
Install scripts npm/core-js@3.23.1
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
  • orphan: npm/core-js@3.23.1
🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/core-js-pure@3.23.1
  • @SocketSecurity ignore npm/core-js@3.23.1