dbcve.org
Plays.tvApplication

CVE-2018-6547

CRITICAL · 9.1 CVSS v3.0 Published 2018-04-13
Fix available
A fix is available. Upgrade to 1.27.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
plays_service.exe in the plays.tv service before 1.27.7.0, as distributed in AMD driver-installation packages and Gaming Evolved products, contains an HTTP message parsing function that takes a user-defined path and writes non-user controlled data as SYSTEM to the file when the extract_files parameter is used. This occurs without properly authenticating the user.

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 confidence

The plays_service.exe contains a path traversal vulnerability in its HTTP message parsing function. An unauthenticated attacker can specify an arbitrary file path via the extract_files parameter, causing the service (running as SYSTEM) to write non-user controlled data to any location on the file system. This enables privilege escalation to SYSTEM and potential code execution.

MitigationUpdate plays.tv service to version 1.27.7.0 or later. If the service is not required, uninstall it to eliminate the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Plays.tvApplication
Affected:< 1.27.7.0

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
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plays_service.exe is present
    Search for plays_service.exe on the system using File Explorer search or the command: dir /s C:\*plays_service.exe (adjust drive letter as needed)
    Affected if The executable exists on the system, indicating plays.tv software is installed
  2. Determine the installed plays.tv version
    Right-click on the plays_service.exe file, select Properties, and examine the Details tab for the Product Version field. Alternatively, check the version via command: wmic product where "name like 'plays.tv%'" get version
    Affected if The version shown is lower than 1.27.7.0 (for example, 1.26.5.0 or similar)
  3. Confirm the plays_service Windows service exists and is running
    Open Services (services.msc) and look for a service named 'plays.tv' or 'plays_service', or run: sc query plays (or sc queryall to list all services and search for plays-related entries)
    Affected if The service exists and is currently running (Status shows RUNNING)
  4. Verify service runs as SYSTEM
    In Services, right-click the plays service, select Properties, and check the 'Log On' account. Alternatively, run: sc qc plays_service (or the service name found in previous step)
    Affected if The service is configured to run under the Local System account (Log on as: Local System account)

The system is affected if plays_service.exe is present, the installed version is below 1.27.7.0, and the service is actively running as Local System account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.27.7.0 or later
Fixed in 1.27.7.0
Interim mitigation

Update plays.tv service to version 1.27.7.0 or later. If the service is not required, uninstall it to eliminate the attack surface.

Recommended fix High confidence

1.27.7.0 or later

  1. 1. Navigate to the official plays.tv website or the AMD driver download page to obtain the latest version.
  2. 2. Download the plays.tv service installer version 1.27.7.0 or later.
  3. 3. If the service is currently running, stop the plays_service.exe process via Task Manager or Services control panel.
  4. 4. Uninstall the existing plays.tv application using Windows Add/Remove Programs.
  5. 5. Run the downloaded installer for version 1.27.7.0 or newer.
  6. 6. Follow the installation wizard prompts to complete the upgrade.
  7. 7. Restart the computer or restart the plays.tv service to ensure the patched version is active.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Plays.tv Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-6547 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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