Parsec Automation TrackSYS: security flaw reported in attacks
OFFICIAL NAME: Parsec Automation TrackSYS pagedefinition direct request
WHAT IT IS · BUSINESS SOFTWAREIt runs day-to-day business work such as finance, printing, phones or manufacturing.
DO THIS FIRSTAsk the vendor or the team that owns it whether the fix is in. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY A vulnerability was found in Parsec Automation TrackSYS 11.x.x and classified as problematic. This issue affects some unknown processing of the file /TS/export/pagedefinition. The manipulation of the argument ID leads to direct request. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269159.
WHY THIS VERDICT Attack attempts are confirmed, with no confirmed exploitation yet.
WHY IT RANKS HERE Ready-made attack tools are public. The first report is 20 days old.
- HIGHEST CONFIRMED RUNG
- TRIED
- CISA KEV
- NOT YET
- EXPLOIT CODE
- READY TO USE
How far has it climbed?
01 TALK
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 1 SOURCEAttack attempts on CVE-2024-6188 seen by honeypots (Shadowserver via CIRCL).
04 EXPLOITED
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICDATE UNKNOWN
- FIRST ATTACK REPORT
- CISA KEV LISTINGNOT YET
- US FEDERAL DEADLINENOT YET
Questions to ask this week
- Do we run Parsec Automation TrackSYS? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- JUN 20, 2024CISA Vulnrichment notes a public proof of concept for CVE-2024-6188
- Attack activity. OCT 21, 2026Attack attempts on CVE-2024-6188 seen by honeypots (Shadowserver via CIRCL)
SOURCES
- [1] nuclei-templates: Nuclei scan template: TrakSYS 11.x.x - Sensitive Data Exposure, OCT 24
- [2] CIRCL Vulnerability-Lookup sightings: Attack attempts on CVE-2024-6188 seen by honeypots (Shadowserver via CIRCL), OCT 21
- [3] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment notes a public proof of concept for CVE-2024-6188, JUN 20