GHSA-qm9f-c3v9-wphv json
Security Update for the OPC UA .NET Standard Stack
published 2y ago modified last yr.
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
This security update resolves a vulnerability in the OPC UA .NET Standard Stack that enables an unauthorized attacker to trigger a rapid increase in memory consumption.
Patch / fix
- nuget OPCFoundation.NetStandard.Opc.Ua.Core 1.05.374.54
- nuget OPCFoundation.NetStandard.Opc.Ua 1.05.374.54
Is GHSA-qm9f-c3v9-wphv in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | OPCFoundation.NetStandard.Opc.Ua.Core | <1.05.374.54 |
1.05.374.54 |
| nuget | OPCFoundation.NetStandard.Opc.Ua | <1.05.374.54 |
1.05.374.54 |
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
Sources
- GitHub Advisory GHSA-qm9f-c3v9-wphv
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.