A vulnerability, which was classified as critical , has been found in Realterm Serial Terminal 2.0.0.70 . Affected by this issue is some unknown functionality. Performing a manipulation results in out-of-bounds write. This vulnerability was named CVE-2019-25569 . The attack needs to be approached locally. In addition, an exploit is available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352354 · CVE-2019-25569 · EXPLOIT 46391
REALTERM SERIAL TERMINAL 2.0.0.70 OUT-OF-BOUNDS WRITE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.6 $0-$5k 1.91+
Summaryinfo
A vulnerability, which was classified as critical, was found in Realterm Serial Terminal 2.0.0.70. This affects an unknown part. Executing a manipulation can lead to out-of-bounds write. The identification of this vulnerability is CVE-2019-25569. The attack can only be executed locally. Furthermore, there is an exploit available.
Detailsinfo
A vulnerability has been found in Realterm Serial Terminal 2.0.0.70 and classified as problematic. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect availability. CVE summarizes:
RealTerm Serial Terminal 2.0.0.70 contains a stack-based buffer overflow vulnerability in the Echo Port field that allows local attackers to crash the application by triggering a structured exception handler (SEH) chain corruption. Attackers can craft a malicious input string with 268 bytes of padding followed by SEH overwrite values and paste it into the Port field to cause denial of service.
The weakness was shared by Alejandra Sánchez as 46391. The advisory is available at exploit-db.com. This vulnerability was named CVE-2019-25569 since 03/21/2026. The exploitation appears to be easy. Local access is required to approach this attack. Technical details are unknown but a public exploit is available.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (46391) and EUVD (EUVD-2019-19886).
Productinfo
Vendor
Realterm
Name
Serial Terminal
Version
2.0.0.70
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.2
CNA Vector (VulnCheck): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Exploit-DB: 🔒
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/21/2026 Advisory disclosed
03/21/2026 +0 days CVE reserved
03/21/2026 +0 days VulDB entry created
03/21/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: 46391
Researcher: Alejandra Sánchez
Status: Not defined
CVE: CVE-2019-25569 (🔒)
GCVE (CVE): GCVE-0-2019-25569
GCVE (VulDB): GCVE-100-352354
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 03/21/2026 15:55
Updated: 03/21/2026 17:13
Changes: 03/21/2026 15:55 (79), 03/21/2026 17:13 (1)
Complete: 🔍
Cache ID: 99:5F9:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸