Skip to content
Fencer Intel
high 7.5

CVE-2017-5177 in the critical feed json

A Stack Buffer Overflow issue was discovered in VIPA Controls WinPLC7 5.0.45.5921 and prior.

published 9y ago modified 4mo ago also EUVD-2017-14286

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.7%
EPSS 17.7% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

A Stack Buffer Overflow issue was discovered in VIPA Controls WinPLC7 5.0.45.5921 and prior. A stack-based buffer overflow vulnerability has been identified, where an attacker with a specially crafted packet could overflow the fixed length buffer. This could allow remote code execution.

Is CVE-2017-5177 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-17-054-01 updated cvss 7.5

VIPA Controls WinPLC7

  • VIPA Controls WinPLC <= 5.0.45.5921
    affected: mitigation “VIPA Controls recommends users install the patch.” google.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. Published
  2. First public exploit (EDB-42693)

Exploit prediction

17.71% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-42693 Viap Automation WinPLC7 5.0.45.5921 - Recv Buffer Overflow (Metasploit) remote, 2017-09-13

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • n/a VIPA Controls WinPLC7

Classification

Weakness
  • CWE-121 Stack-based Buffer Overflow
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.