A vulnerability labeled as problematic has been found in VSCO 1.1.1.0 . This vulnerability affects unknown code of the component Search . Such manipulation leads to improper handling of overlap between protected memory ranges. This vulnerability is listed as CVE-2018-25238 . The attack must be carried out locally. In addition, an exploit is available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355359 · CVE-2018-25238 · EXPLOIT 46385
VSCO 1.1.1.0 SEARCH OVERLAP BETWEEN PROTECTED MEMORY RANGES
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.6 $0-$5k 0.14+
Summaryinfo
A vulnerability marked as problematic has been reported in VSCO 1.1.1.0. This issue affects some unknown processing of the component Search. Performing a manipulation results in improper handling of overlap between protected memory ranges. This vulnerability is cataloged as CVE-2018-25238. The attack must be initiated from a local position. Furthermore, there is an exploit available.
Detailsinfo
A vulnerability, which was classified as problematic, was found in VSCO 1.1.1.0. This affects an unknown code of the component Search. The manipulation with an unknown input leads to a improper handling of overlap between protected memory ranges vulnerability. CWE is classifying the issue as CWE-1260. The product allows address regions to overlap, which can result in the bypassing of intended memory protection. This is going to have an impact on availability. The summary by CVE is:
VSCO 1.1.1.0 contains a denial of service vulnerability that allows local attackers to crash the application by submitting an excessively long string through the search functionality. Attackers can paste a buffer of 5000 characters into the search bar and navigate back to trigger an application crash.
The weakness was shared by 0xB9 as 46385. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2018-25238 since 04/04/2026. The exploitability is told to be easy. Attacking locally is a requirement. Technical details are unknown but a public exploit is available.
The exploit is shared for download 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 (46385).
Productinfo
Name
VSCO
Version
1.1.1.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: 46385
Researcher: 0xB9
Status: Not defined
CVE: CVE-2018-25238 (🔒)
GCVE (CVE): GCVE-0-2018-25238
GCVE (VulDB): GCVE-100-355359
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 04/04/2026 19:45
Changes: 04/04/2026 19:45 (78)
Complete: 🔍
Cache ID: 99:031:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸