Skip to main content
Mallory
HighVulnerability

CVE-2017-5177: Stack Buffer Overflow in VIPA Controls WinPLC7

Published May 19, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3
EPSS17.7%97th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Vipa Controls
IdentifiersCVE-2017-5177CWE-121 · Stack-based Buffer Overflow

A stack-based buffer overflow vulnerability exists in VIPA Controls WinPLC7 version 5.0.45.5921 and prior. The vulnerability is triggered when the application processes a specially crafted packet, which overflows a fixed-length buffer on the stack. This can potentially allow an attacker to execute arbitrary code on the affected system.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability could allow a remote attacker to execute arbitrary code with the privileges of the application, leading to full system compromise. This is particularly critical in industrial control environments where WinPLC7 is deployed.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the affected system to trusted hosts only. Employ network segmentation and firewall rules to limit exposure. Monitor network traffic for suspicious or malformed packets targeting the application.

Remediation

Patch, then assume compromise.

Upgrade to a version of VIPA Controls WinPLC7 later than 5.0.45.5921 where this vulnerability has been addressed. If an update is not available, contact the vendor for further guidance.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Vipa ControlsWinplc7 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2017-5177 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-5177 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-5177?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2017-5177. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2017-5177?
Upgrade to a version of VIPA Controls WinPLC7 later than 5.0.45.5921 where this vulnerability has been addressed. If an update is not available, contact the vendor for further guidance.
What products are affected by CVE-2017-5177?
Vipa Controls Winplc7 Firmware.
How severe is CVE-2017-5177?
CVE-2017-5177 has a CVSS v3 score of 7.5 (High) and an EPSS score of 17.7% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.