Ua-.netstandard vulnerabilitiesRanked by how likely they are to be used.
Ua-.netstandard is made by Opcfoundation. We track 6 published vulnerabilities in it, across 14 versions. None of them is on the list of flaws known to be exploited today. If you run Ua-.netstandard, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Ua-.netstandard vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ua-.netstandard's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ua-.netstandard flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.2%CVE-2018-7559Medium
An issue was discovered in OPC UA .NET Standard Stack and Sample Code before GitHub commit 2018-04-12, and OPC UA .NET Legacy Stack and Sample Code before GitHub commit 2018-03-13.
- 1.0%CVE-2023-27321High
OPC Foundation UA .NET Standard ConditionRefresh Resource Exhaustion Denial-of-Service Vulnerability.
- 1.0%CVE-2019-19135High
In OPC Foundation OPC UA .NET Standard codebase 1.4.357.28, servers do not create sufficiently random numbers in OPCFoundation.NetStandard.Opc.Ua before 1.4.359.31, which allows man in the middle attackers to reuse...
- 0.8%CVE-2023-31048Medium
The OPC UA .NET Standard Reference Server before 1.4.371.86.
- 0.3%CVE-2020-29457Medium
A Privilege Elevation vulnerability in OPC UA .NET Standard Stack 1.4.363.107 could allow a rogue application to establish a secure connection.
- 0.3%CVE-2018-12087Medium
Failure to validate certificates in OPC Foundation UA Client Applications communicating without security allows attackers with control over a piece of network infrastructure to decrypt passwords.
Running Ua-.netstandard? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An issue was discovered in OPC UA .NET Standard Stack and Sample Code before GitHub commit 2018-04-12, and OPC UA .NET Legacy Stack and Sample Code before GitHub commit 2018-03-13. A vulnerability in OPC UA applications can allow a remote attacker to determine a Server's private key by sending carefully constructed bad UserIdentityTokens as part of an oracle attack.
- Matched to
- Ua-.netstandard on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Ua-.netstandard, across 14 versions.
None of Ua-.netstandard's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Ua-.netstandard. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.