A vulnerability was found in Watchr 1.1.0.0 . It has been declared as problematic . Affected is an unknown function of the component Search . Executing a manipulation can lead to improper handling of overlap between protected memory ranges. The identification of this vulnerability is CVE-2018-25240 . The attack can only be executed locally. Furthermore, there is an exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355355 · CVE-2018-25240 · EXPLOIT 46194
WATCHR 1.1.0.0 SEARCH OVERLAP BETWEEN PROTECTED MEMORY RANGES
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.6 $0-$5k 0.83+
Summaryinfo
A vulnerability was found in Watchr 1.1.0.0. It has been rated as problematic. Affected by this vulnerability is an unknown functionality of the component Search. The manipulation leads to improper handling of overlap between protected memory ranges. This vulnerability is referenced as CVE-2018-25240. The attack can only be performed from a local environment. Furthermore, an exploit is available.
Detailsinfo
A vulnerability was found in Watchr 1.1.0.0. It has been rated as problematic. This issue affects an unknown function of the component Search. The manipulation 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:
Watchr 1.1.0.0 contains a denial of service vulnerability that allows local attackers to crash the application by submitting an excessively long string to the search functionality. Attackers can paste a buffer of 8145 characters into the search bar and trigger a search operation to cause the application to crash.
The weakness was published by 0xB9 as 46194. It is possible to read the advisory at exploit-db.com. The identification of this vulnerability is CVE-2018-25240 since 04/04/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details are unknown but a public exploit is available.
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 vulnerability database at Exploit-DB (46194).
Productinfo
Name
Watchr
Version
1.1.0.0
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: Improper handling of overlap between protected memory ranges
CWE: CWE-1260 / 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
04/04/2026 Advisory disclosed
04/04/2026 +0 days CVE reserved
04/04/2026 +0 days VulDB entry created
04/04/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: 46194
Researcher: 0xB9
Status: Not defined
CVE: CVE-2018-25240 (🔒)
GCVE (CVE): GCVE-0-2018-25240
GCVE (VulDB): GCVE-100-355355
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 04/04/2026 19:44
Changes: 04/04/2026 19:44 (78)
Complete: 🔍
Cache ID: 99:E2B:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸