Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Jimmy John's Gourmet Sandwiches POS Systems Hacked
Newest First  |  Oldest First  |  Threaded View
Some Consultant
50%
50%
Some Consultant,
User Rank: Apprentice
9/25/2014 | 12:57:57 PM
Easier to wait for the incident and then pay
The way this works is the classic "show me the money" fashion. Security costs money and it is seen (until a breach happens) as an unneeded expense. Another common "modus operandi" we find here is to use a relaxed vendor to gain access to your infrastructure (do you remember Target?). It seems to me that paying with cash will become the way payment in America. 
Kelly Jackson Higgins
100%
0%
Kelly Jackson Higgins,
User Rank: Strategist
9/25/2014 | 11:25:28 AM
Re: Once again..
Note that Jimmy John's response is that it now has installed encrypted POS terminals in the stores. 
aws0513
50%
50%
aws0513,
User Rank: Ninja
9/25/2014 | 9:38:37 AM
Listing of stores is a good response tactic
As much as it saddens me to see another POS compromise victim, the way Jimmy Johns is responding to the compromise is commendable.  To provide a list of affected stores demonstrates a willingness to engage their customers even in the worst of situations. 
Of course, one would have to trust the provided list is accurate.
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
9/25/2014 | 6:53:17 AM
Once again..
Once again POS system exposed, security in retailer world is an optional and recent cases demonstrate it. It's time to completely change the approach to security to avoid a dramatic domino effect.

Such incidents expose users to financial losses, but also to identity theft risk and the worrying aspect is that in the majority of cases the data breached go undetected for months.


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-29379
PUBLISHED: 2021-04-12
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on D-Link DIR-802 A1 devices through 1.00b05. Universal Plug and Play (UPnP) is enabled by default on port 1900. An attacker can perform command injection by injecting a payload into the Search Target (ST) field of the SSDP M-SEARCH discover pa...
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.