Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-17528

backends/platform/sdl/posix/posix.cpp in ScummVM 1.9.0 does not valida ...

Overview

Published
14 Dec 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
2 OS packages
4 Linux distributions
Yes Fix available

Description

backends/platform/sdl/posix/posix.cpp in ScummVM 1.9.0 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Weakness: CWE-74

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

debian 4 releases · 1 package

affected 4
scummvm
debian fixes for CVE-2017-17528
ReleasePackageFixed in
11 scummvm affected
12 scummvm affected
13 scummvm affected
14 scummvm affected

echo 1 release · 1 package

affected 1
scummvm
echo fixes for CVE-2017-17528
ReleasePackageFixed in
scummvm affected

openSUSE 1 release · 1 package

fixed 1
scummvm
openSUSE fixes for CVE-2017-17528
ReleasePackageFixed inAdvisory
Tumbleweed scummvm +1 2.2.0-3.3 openSUSE-SU-2024:11375-1

ubuntu 5 releases · 1 package

affected 5
scummvm
ubuntu fixes for CVE-2017-17528
ReleasePackageFixed in
18.04-ESM scummvm affected
20.04-ESM scummvm affected
22.04 scummvm affected
24.04 scummvm affected
26.04 scummvm affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.