LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25602: GSearch 1.0.1.0 Denial of Service via Search Input

GSearch 1.0.1.0 contains a denial of service vulnerability that allows local attackers to crash the application by inputting an excessively long string in the search bar. Attackers can paste a buffer of 2000 characters into the search field, click search, and select any result to trigger an application crash.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25602 is a local denial-of-service issue in GSearch 1.0.1.0. A person with access to the application can crash it through oversized search input. This does not indicate data theft or system takeover, but it can disrupt users who rely on the app.

Executive priority

Treat as a moderate operational-risk item. Address where the application is business-critical, shared, or exposed to untrusted local users. It is not currently supported by the provided sources as a remote compromise or active exploitation emergency.

Technical view

The vulnerability affects GSearch 1.0.1.0 and is described as a crash triggered through the search interface after excessively long input. CVSS 4.0 score is 6.8, with local attack vector, low complexity, no privileges, and user interaction present. Impact is high availability loss for the vulnerable application only.

Likely exposure

Exposure is limited to systems where GSearch 1.0.1.0 is installed and accessible to a local user. The provided sources do not identify server-side, remote, or enterprise-wide exposure.

Exploitation context

A public Exploit-DB reference exists, but the source bundle does not show CISA KEV listing or confirmed active exploitation. The issue requires local application interaction and causes an application crash rather than confidentiality or integrity compromise.

Researcher notes

Evidence is narrow and product-specific. CVE metadata and VulnCheck describe GSearch 1.0.1.0 only. Exploit-DB indicates public exploit information, but this assessment does not include weaponization details. No patch version is named in the supplied sources.

Mitigation direction

  • Inventory endpoints for GSearch 1.0.1.0 installations.
  • Check vendor or Microsoft Store guidance for updates or replacement versions.
  • Remove GSearch where it is not business-required.
  • Restrict use of affected installations to trusted local users.
  • Prioritize remediation for shared kiosks or multi-user workstations.

Validation and detection

  • Confirm whether GSearch 1.0.1.0 is installed on managed endpoints.
  • Review software inventory data for the Microsoft Store product reference.
  • Check vendor advisory sources for updated affected-version or fix information.
  • Avoid crash testing on production systems unless approved.
  • Document business owners for any remaining installations.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1260: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25602 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.8Medium
CVSS 4.0 vector shape for CVE-2019-25602Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GSearchGSearch1.0.1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1260 · source CWE mapping

Improper Handling of Overlap Between Protected Memory Ranges

Improper Handling of Overlap Between Protected Memory Ranges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.