Communications Subscriber-Aware Load Balancer vulnerabilitiesRanked by how likely they are to be used.
Communications Subscriber-Aware Load Balancer is made by Oracle. We track 2 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Subscriber-Aware Load Balancer, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Subscriber-Aware Load Balancer vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Subscriber-Aware Load Balancer's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Subscriber-Aware Load Balancer 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.
- 7.1%CVE-2020-1971Medium
The X.509 GeneralName type is a generic type for representing different types of names.
- 5.2%CVE-2020-8203High
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
Running Communications Subscriber-Aware Load Balancer? 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
The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).
- Matched to
- Communications Subscriber-Aware Load Balancer 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 2 published vulnerabilities listed under the name Communications Subscriber-Aware Load Balancer, across 3 versions.
None of Communications Subscriber-Aware Load Balancer's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Subscriber-Aware Load Balancer. 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.