IOT-Yocto vulnerabilitiesRanked by how likely they are to be used.
IOT-Yocto is made by Linuxfoundation. We track 15 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run IOT-Yocto, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which IOT-Yocto vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of IOT-Yocto's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which IOT-Yocto 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.
- <0.1%CVE-2023-20740Medium
In vcu, there is a possible memory corruption due to a logic error.
- <0.1%CVE-2023-20744Medium
In vcu, there is a possible use after free due to a logic error.
- <0.1%CVE-2023-20734Medium
In vcu, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20738Medium
In vcu, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20735Medium
In vcu, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20715Medium
In wlan, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20712Medium
In wlan, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20716Medium
In wlan, there is a possible out of bounds write due to a missing bounds check.
- <0.1%CVE-2023-20747Medium
In vcu, there is a possible memory corruption due to type confusion.
- <0.1%CVE-2023-20737Medium
In vcu, there is a possible use after free due to improper locking.
Running IOT-Yocto? 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
In vcu, there is a possible memory corruption due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07559819; Issue ID: ALPS07559840.
- Matched to
- IOT-Yocto 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 15 published vulnerabilities listed under the name IOT-Yocto, across 1 version.
None of IOT-Yocto's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track IOT-Yocto. 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.