Bro up to 2.3.1 DNP3 Packet memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Bro up to 2.3.1. It has been declared as problematic. This vulnerability affects an unknown function of the file analyzer/protocol/dnp3/ of the component DNP3 Packet Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The software performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. CVE summarizes:

analyzer/protocol/dnp3/ in Bro before 2.3.2 does not reject certain non-zero values of a packet length, which allows remote attackers to cause a denial of service (buffer overflow or buffer over-read) via a crafted DNP3 packet.

The bug was discovered 01/24/2015. The weakness was disclosed 04/24/2017 (GitHub Repository). The advisory is shared for download at This vulnerability was named CVE-2015-1522 since 02/06/2015. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 821 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 2.3.2 eliminates this vulnerability.

The entry 100491 is pretty similar.




  • open-source

CPE 2.3info

CPE 2.2info


VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.1

VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Memory corruption
CWE: CWE-119
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Bro 2.3.2


01/24/2015 🔍
02/06/2015 +13 days 🔍
04/24/2017 +808 days 🔍
04/24/2017 +0 days 🔍
04/24/2017 +0 days 🔍
12/02/2022 +2048 days 🔍


Advisory: 6cedd67c381ff22fde653adf02ee31caf66c81a0
Status: Not defined
Confirmation: 🔍

CVE: CVE-2015-1522 (🔍)
OSVDB: - CVE-2015-1522 - Bro - Buffer Overflow Issue

See also: 🔍


Created: 04/24/2017 02:39 PM
Updated: 12/02/2022 08:40 AM
Changes: 04/24/2017 02:39 PM (59), 09/20/2020 11:27 AM (3), 12/02/2022 08:40 AM (5)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!