Realterm Serial Terminal 2.0.0.70 Port overlap between protected memory ranges
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Realterm Serial Terminal 2.0.0.70 and classified as problematic. This vulnerability affects unknown code. The manipulation of the argument Port leads to improper handling of overlap between protected memory ranges. This vulnerability is referenced as CVE-2019-25570. The attack can only be performed from a local environment. Furthermore, an exploit is available.
Details
A vulnerability was found in Realterm Serial Terminal 2.0.0.70 and classified as problematic. This issue affects an unknown part. The manipulation of the argument Port with an unknown input leads to a improper handling of overlap between protected memory ranges vulnerability. Using CWE to declare the problem leads to CWE-1260. The product allows address regions to overlap, which can result in the bypassing of intended memory protection. Impacted is availability. The summary by CVE is:
RealTerm Serial Terminal 2.0.0.70 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the Port field. Attackers can paste a buffer of 1000 characters into the Port input field and click the open button to trigger a crash.
The weakness was published by Alejandra Sánchez as 46390. It is possible to read the advisory at exploit-db.com. The identification of this vulnerability is CVE-2019-25570 since 03/21/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details as well as a public exploit are known.
The exploit is available 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 (46390) and EUVD (EUVD-2019-19888). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CNA Base Score: 5.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Improper handling of overlap between protected memory rangesCWE: CWE-1260 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/21/2026 Advisory disclosed03/21/2026 CVE reserved
03/21/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Advisory: 46390Researcher: Alejandra Sánchez
Status: Not defined
CVE: CVE-2019-25570 (🔒)
GCVE (CVE): GCVE-0-2019-25570
GCVE (VulDB): GCVE-100-352355
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/21/2026 15:55Updated: 03/27/2026 16:28
Changes: 03/21/2026 15:55 (79), 03/21/2026 17:13 (1), 03/27/2026 16:28 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.