This is page 3 of:
Forgotten Apps Pose PCI Danger, Visa List Shows
June 10th, 2010
ConnectUp. All versions.
PopsOn. All versions.
ProtoBase V4.80.xx.
ProtoBase V4.7x.xx.
PBAdmin V4.01.xx.
PBAdmin V5.00.xx.
G-SITE ADS G-SITE ADS–Chicago. All versions prior to V22.1.0.3.
G-SITE Concord/Buypass. All versions prior to V6.4.03.
G-SITE Exxon Mobil. All versions prior to and including V4.8.38.
EVS V1.
ACE Electronic Payment Support (EPS) V5. All levels prior to P150.
ACE Electronic Payment Support (EPS) V4. All levels prior to N166.
ACE Electronic Payment Support (EPS) V3. All levels prior to M207.
StorePay. All versions prior to V5.0.
Message Sentry V1 for Unix.
Message Sentry V1 for Mainframe.
Payment Switch Framework Authorization & Settlement Suite V1.0.
8700 HMS V2.50 through V2.50.20*.
8700 HMS V2.11.0 through V2.11.9*.
8700 HMS V1.00 through V2.10.
9700 HMS. All versions prior to V2.50.
Opera Enterprise Solution V5.0.
Opera Enterprise Solution V4.0.1.
Opera Enterprise Solution V4.04.02.
Opera Enterprise Solution V3.6.1E03.
RES V3.2.0*.
RES V3.1.0*.
RES V1 through V3.0.
WinPM V1.80.
WinPM V1.63.
WinPM V1.62.
ScanMaster. All 2.0.xx.xx Versions prior to V2.00.03.12.
ScanMaster. All 1.2.xx.xx versions prior to V1.2.3.26.
ScanMaster V1.1.6.xx.
Maitre’D. All versions prior to V2003 Service Pack 11.
Maitre’D. All versions of V2002.
RPOS (Petroleum and Convenience Stores). All versions where sites accept debit card transactions at the Island Card Reader higher than and including V5.3 and V6.6.
Retail Pro. All versions prior to and including V8.52.xx.xx.
Ruby, Topaz Buypack (First Data) V4.01.xx.
Ruby, Topaz Buypack (First Data) V2.10.xx.
Ruby, Topaz Buypack (First Data) V2.09.xx.
Ruby, Topaz Buypack (First Data) V2.08.xx.
Ruby, Topaz (Store & Forward Fleet and Debit) Buypack (First Data) V4.07.xx.
Ruby, Topaz (Store & Forward Fleet and Debit) Buypack (First Data) V4.06.xx.
June 10th, 2010 at 11:43 am
I have no idea the reason Visa or PCI SSC does not publicly post this list. I have two guesses: 1) legal reasons — Visa is affraid they’ll be sued for libel? or 2) security reasons like you mentioned — but hackers have a better network for distributing this information and most likely already know these vulnerable apps and many more.
*The asterisks next to the various Micros versions indicate that there are secure third party drivers that can bring them into compliance.
July 1st, 2010 at 7:08 pm
It’s logical not to publish the list, although I would personally benefit from its publication.
Two of my competitors are on the list, but the systems listed are very old. Many consumers would look at the brand name and just reject them as potential choices to be on the safe side. VISA doesn’t want it list to be a kiss of death for an established brand.