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
PINs Stolen In Target Breach
Oldest First  |  Newest First  |  Threaded View
SubtleLogic
50%
50%
SubtleLogic,
User Rank: Apprentice
12/31/2013 | 9:46:16 PM
re: PINs Stolen In Target Breach
Uh, the current standards in the financial industry dictate the use of triple DES for encrypting PINs so this not something Target chooses to use, nor would any security or PCI audit have any problems with this.

It's still not trivial to crack TDES encryption, and the end result would only be one PIN. The effort is not worth it, especially when the unprotected track data can be used so easily.

Too many "experts" offering opinions on the Target hack.
Mark Bower
50%
50%
Mark Bower,
User Rank: Apprentice
1/3/2014 | 1:26:04 AM
re: PINs Stolen In Target Breach
Unless the attackers have the keys from every device, which is very unlikely, retrieving PIN numbers will be impossible for all intents and purposes, even to determined attackers. Correctly implemented Triple-DES is still resilient to brute force attacks with 168-bits of encryption strength. It should not be confused with Single-DES 56 bit encryption. To retrieve PIN's an attacker would need to physically retrieve each unique PIN encryption key from every PIN entry device - quite a challenge. The devices for PIN entry are also likely PCI-PTS (and card scheme) validated which ensures physical and logical tamper detection is effective to erase PIN keys and other sensitive data in the event of detected compromise such as device being drilled into, put into a spurious operating condition and so on.

Strong PIN encryption has been with us for some time, and encrypted PIN's are routinely transmitted over open networks. It is well defined in ANSI standards and proven. The point of encryption is to protect from inadvertent compromise.

The details of why this is true are nicely and accurately summarized by Matt Green from John Hopkins University including comments on the PCI aspect:

http://blog.cryptographyengine...

Disclaimer - I work for a vendor in the data protection industry providing end-to-end protection of payment cardholder data for major retailers and acquirers.

Regards,
Mark Bower
VP Product Management and Solution Architecture
Voltage Security, Inc.
Guest
50%
50%
Guest,
User Rank: Apprentice
1/3/2014 | 8:44:47 PM
re: PINs Stolen In Target Breach
I may be ignorant on this, but can't you guess what the known plaintext would be... There are only 10,000 possibilities: 0000 to 9999
LucasZa
50%
50%
LucasZa,
User Rank: Moderator
1/9/2014 | 9:49:18 PM
re: PINs Stolen In Target Breach
There isn't a mechanism to "guess the PIN" against the ciphertext and get back a yes/no answer. Known plain text attacks don't work against modern ciphers including TDES. That would be considered a tremendous weakness. The only way to decrypt is to have the key or guess it. Think of it this way: Let's say there's a piece of paper in a lockbox with a 4 digit number. Yelling 4 digit numbers at the lockbox isn't going to make it open up if you guess right. The criminals could clone cards and try guessing PINs at ATM machines, but a few failed attempts would cause the card to go on security hold and fraud monitoring departments would notice after a few cards are attempted.


Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5613
PUBLISHED: 2020-02-18
In FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13, a missing check in the ipsec packet processor allows reinjection of an old packet to be accepted by the ipsec endpoint. Depending on the higher-level protocol in use over ipsec, this could allow an action to be repeated.
CVE-2020-7450
PUBLISHED: 2020-02-18
In FreeBSD 12.1-STABLE before r357213, 12.1-RELEASE before 12.1-RELEASE-p2, 12.0-RELEASE before 12.0-RELEASE-p13, 11.3-STABLE before r357214, and 11.3-RELEASE before 11.3-RELEASE-p6, URL handling in libfetch with URLs containing username and/or password components is vulnerable to a heap buffer over...
CVE-2019-10792
PUBLISHED: 2020-02-18
bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10793
PUBLISHED: 2020-02-18
dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10794
PUBLISHED: 2020-02-18
All versions of component-flatten are vulnerable to Prototype Pollution. The a function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.