Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade node-opcua from 2.81.0 to 2.120.0 #267

Closed
wants to merge 1 commit into from

Conversation

biancode
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 631/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.2
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
No Proof of Concept
high severity 768/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Observable Discrepancy
SNYK-JS-JSRSASIGN-6070731
No Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: node-opcua The new version differs by 250 commits.
  • f4ae243 v2.120.0
  • a0234bb update packages
  • 2e6d593 update book url
  • 85bee18 update lock fil
  • 521f18d fixes #1277 - instantiating ObjectType with two Folders
  • 45240f8 add example for github #1232
  • af35205 update copyright year
  • f3d452b fix copyright year and other adjustments
  • 37e1816 add open collective badges
  • 744648e relax Encoding detection to cope with bugs in python's asyncua - fixing #1232
  • 56b40b1 ClientSecureChannel: fix connection issue hightlighted when server impose maxChunk=1 #1335
  • 2372431 ensure client.isReconnecting=true when client emits the 'connection_reestablished' event fix#1331
  • cb434af v2.119.2
  • a2d882f chore: unset debug flag
  • 1f75a25 node-opcua-nodeset: refactor index_web
  • 78fba90 v2.119.1
  • 4b809b9 chore: add missing data folder in package
  • f985d1a v2.119.0
  • 0270f16 update packages
  • c70438e fix ConditionVariableType behavior with SourceTimestamp property
  • 84b55ee allow effectiveTransitionTime to be passed when setting a TwoStateVarialbe for instance UACondition#setEnableState(true, { effectiveTransitionTime: somedate})
  • 200e233 allow time and receiveTime to be optionally passed on raiseNewCondition
  • 734c0d9 isssue #1303 refactor: Add 'host' parameter to OPCUAServer for specific interface binding
  • 77f1bf6 fix MultiStateValueDiscrete behavior #1323

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

Greet Contributors Bot
Thank you for taking your time and effort for your contribution, we truly value it. 🎉

The amazing contributor in this pull request is @snyk-bot

@biancode biancode closed this Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants