CVE-2015-0310Adobe Flash Player ASLR Bypass Vulnerability
CVE-2015-0310 is a information exposure in Adobe Flash Player, rated high (7.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
The software reveals data to someone who should not see it.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker learn data or internals that help a follow-up attack.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2022-05-25: it is being exploited in the wild. EPSS estimates a 15% chance of exploitation activity in the next 30 days, higher than 97% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-06-15.
- Upgrade Adobe Flash Player to a fixed version for your release line (13.0.0.262, 16.0.0.287). The patch notes are linked below.
- Limit who can run code or sign in on the hosts that run it.
- Warn the people who use it, and filter files and links on the way in.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
Adobe Flash Player before 13.0.0.262 and 14.x through 16.x before 16.0.0.287 on Windows and OS X and before 11.2.202.438 on Linux does not properly restrict discovery of memory addresses, which allows attackers to bypass the ASLR protection mechanism on Windows, and have an unspecified impact on other platforms, via unknown vectors, as exploited in the wild in January 2015.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does Adobe Flash Player run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Advisories
Issue reports
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.