CVE-2019-25327
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 · uneditedPrime95 version 29.8 build 6 contains a buffer overflow vulnerability in the user ID input field that allows remote attackers to execute arbitrary code. Attackers can craft a malicious payload and paste it into the PrimeNet user ID and proxy host fields to trigger a bind shell on port 3110.
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 confidencePrime95 29.8 build 6 contains a stack-based buffer overflow in the PrimeNet user ID and proxy host input fields. Attackers can inject a malicious payload that triggers a bind shell on port 3110, achieving remote code execution without authentication.
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 Prime95 installationSearch for prime95.exe on the system or check Program Files directories for Prime95 installation foldersAffected if Prime95 software is present on the machine
-
Check Prime95 versionRight-click on prime95.exe, select Properties, and view the File Version field. Compare against 29.8 build 6Affected if Version is 29.8 build 6 or earlier
-
Verify PrimeNet is configuredLook for prime.txt or local.txt configuration files in the Prime95 directory. Check for user_id or proxy_host settingsAffected if PrimeNet user ID or proxy host fields are configured or accessible through the PrimeNet communication settings
-
Monitor for suspicious port 3110 listeningRun netstat -an | findstr 3110 or use PowerShell Get-NetTCPConnection -LocalPort 3110 to check if port 3110 is in LISTEN stateAffected if Port 3110 is open and listening, indicating potential compromise from the bind shell payload
-
Check for unexpected Prime95 processesReview running processes for prime95.exe instances with unusual parent processes or command line argumentsAffected if Prime95 is running with network-listening behavior or spawned by an unexpected parent process
A system is affected if Prime95 version 29.8 build 6 or earlier is installed AND PrimeNet communication features are enabled, with port 3110 being the key indicator of active exploitation.
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 dataUpgrade to a patched version of Prime95 immediately. If upgrading is not feasible, block inbound/outbound traffic on port 3110 at the network perimeter and restrict access to the PrimeNet communication features.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25327 — 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-25327 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