CVE-2019-25319
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDomain Quester Pro 6.02 contains a stack overflow vulnerability that allows remote attackers to execute arbitrary code by overwriting Structured Exception Handler (SEH) registers. Attackers can craft a malicious payload targeting the 'Domain Name Keywords' input field to trigger an access violation and execute a bind shell on port 9999.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDomain Quester Pro 6.02 has a stack-based buffer overflow vulnerability in the 'Domain Name Keywords' input field. Attackers can overflow the stack with excessive input to overwrite Structured Exception Handler (SEH) registers, allowing arbitrary code execution via a bind shell on port 9999.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Domain Quester Pro installationCheck system for Domain Quester Pro application - look in Program Files, Program Files (x86), or use system search for the application nameAffected if Domain Quester Pro is installed on the system
-
Determine installed versionRight-click the application executable, select Properties, and check the Version tab; or launch the application and look in Help > AboutAffected if The installed version matches 6.02 or is unknown/unlisted (treat as affected)
-
Assess network exposureCheck firewall rules and network configuration to determine if the application or its ports are accessible from external sourcesAffected if The application is accessible from untrusted network sources or the internet
-
Verify input source exposureDetermine whether the 'Domain Name Keywords' input field can receive data from untrusted or remote sources rather than only local trusted inputAffected if The Domain Name Keywords field can process input from untrusted or remote sources
-
Check for anomalous network listenersUse netstat or similar tool to check if the application is listening on port 9999 or other unexpected portsAffected if The application is listening on port 9999 or has unexpected open ports
The environment is affected if Domain Quester Pro version 6.02 is installed and the application or its Domain Name Keywords input field is exposed to untrusted network input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to systems running Domain Quester Pro and avoid exposing the application to untrusted networks until a vendor patch or upgrade path is available; implement strict input length validation on all user-provided fields.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-25319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data