Skip to content
Fencer Intel
high 7.8

CVE-2017-14627 in the critical feed json

Stack-based buffer overflows in CyberLink LabelPrint 2.5 allow remote attackers to execute arbitrary code via the (1) author (inside the IN…

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

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
19.0%
EPSS 19.0% chance of exploitation in 30 days, percentile 97%
public exploits
3
Metasploit and Exploit-DB

Summary

Stack-based buffer overflows in CyberLink LabelPrint 2.5 allow remote attackers to execute arbitrary code via the (1) author (inside the INFORMATION tag), (2) name (inside the INFORMATION tag), (3) artist (inside the TRACK tag), or (4) default (inside the TEXT tag) parameter in an lpp project file.

Is CVE-2017-14627 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

Timeline

  1. First public exploit (Metasploit exploit/windows/fileformat/cyberlink_lpp_bof)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/windows/fileformat/cyberlink_lpp_bof CyberLink LabelPrint 2.5 Stack Buffer Overflow metasploit exploit, normal rank, 2017-09-23
  • EDB-45985 CyberLink LabelPrint 2.5 - Stack Buffer Overflow (Metasploit) local, 2018-12-13
  • EDB-42777 CyberLink LabelPrint < 2.5 - Local Buffer Overflow (SEH Unicode) local, 2017-09-23
  • blog.spentera.com https://blog.spentera.com/2017/09/19/unicode-stack-based-buffer-overflow-on-cyberlink-labelprint-2-5/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • 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.