Debian LinuxOperating system · Debian

CVE-2017-5208

HIGH · 8.8 CVSS v3.0 Published 2017-08-22
Fix available
A fix is available. Upgrade to 0.31.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Integer overflow in the wrestool program in icoutils before 0.31.1 allows remote attackers to cause a denial of service (memory corruption) via a crafted executable, which triggers a denial of service (application crash) or the possibility of execution of arbitrary code.

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

Integer overflow in the wrestool program of icoutils (versions before 0.31.1) allows processing of crafted executables to cause memory corruption, leading to denial of service (application crash) or potentially arbitrary code execution.

MitigationUpgrade icoutils to version 0.31.1 or later to patch the integer overflow vulnerability. Verify no other affected versions remain in the environment.

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
Debian LinuxOperating system
Affected:= 8.0
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.3= 7.4= 7.6
Enterprise Linux Server EusOperating system
Affected:= 7.3= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
Affected:= 7.3= 7.6
Enterprise Linux WorkstationOperating system
Affected:= 7.0
IcoutilsApplication
Affected:< 0.31.1

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
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

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 icoutils package is installed
    On Debian-based systems: dpkg -l | grep icoutils. On RHEL-based systems: rpm -qa | grep icoutils
    Affected if The package is installed and its version is below 0.31.1
  2. Determine wrestool version
    Run 'wrestool --version' or 'wrestool -V' to obtain the exact version number of the wrestool binary
    Affected if The reported version is less than 0.31.1 (for icoutils source) or the package version is older than the version shipped in RHEL 7.3+/Debian 8 updates
  3. Check if wrestool processes untrusted executables
    Review any scripts, automation, or workflows that invoke wrestool on input files from untrusted sources (e.g., downloaded PE executables, third-party binaries)
    Affected if wrestool is used to process executable files from untrusted or external sources without verification
  4. Confirm vulnerability trigger condition
    The flaw is triggered when wrestool parses a crafted Win32 executable (PE format). No specific config toggle exists; the bug is in the parsing logic itself.
    Affected if Any use of wrestool on potentially malicious or unvalidated PE executables could trigger the integer overflow

You are affected if icoutils/wrestool is installed with a version below 0.31.1 and you use it to process executable files from untrusted sources.

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.

From vendor data
Upgrade available Upgrade to 0.31.1 or later
Fixed in 0.31.1
Interim mitigation

Upgrade icoutils to version 0.31.1 or later to patch the integer overflow vulnerability. Verify no other affected versions remain in the environment.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5208 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5208 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