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.

Risk

1/24/2007
03:55 AM
50%
50%

Pushback on Chargebacks

User data inside browser could hold the key to reducing online fraud and losses

1:55 PM -- I've been interested in passive and active sniffing of browsers for a long time. One thing I really don't think has been touched often enough is the bridge between business economics and the types of users who visit Websites. More than just their height, age, or IP address, what else is available to us?

Companies like Cybersource do all sorts of interesting charge-back ratio prevention analysis. For instance, they look at the sex of the user. Why? Because a woman signing up for a porn site is a very high predictor of fraud and, therefore, chargebacks.

For anyone not familiar with how chargebacks work, merchants have to wait up to six months before the various credit card companies stop allowing their consumers to ask for their money back. Each chargeback not only costs the merchant money but it also can add up in fines. If your chargeback ratio is too high, you can be fined thousands of dollars a day until your chargeback ratios return to a reasonable level.

That's a big hit for merchants that will either cause companies to go out of business, pass the costs back to the consumer, or eat the charges. Any way you slice it, it's bad business.

What if there were a way for the merchant to look into the consumer's computer and find out information about it. Perhaps knowing more about the user would raise flags.

One simple example of this is the browser user-agent header. Are you more likely to trust someone who has Internet Explorer or Firefox to perform a transaction? Well, Firefox users tend to be more Web-savvy. And such users tend to be more on the cutting edge of technology, so they are more likely to abuse the system, commit fraud, or at the very least know how to charge back a credit card fee.

But can something as simple as a user agent tell merchants who they should be doing business with online?

If that were the case, there are dozens of things merchants could look at. Some spyware leaves signatures, and browsers often tell you that they've got firewalls installed. There are hundreds of variables and variants that could point to a higher or lower level of suspicion based on the signatures that every browser sends.

Of course, this is all theory. I don't have any data to back it up. Anyone want to let me have access to all their financial transactions and traffic to do chargeback analytics? It's a hard thing to sell, but it could mean big savings on chargeback for online businesses.

— RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18575
PUBLISHED: 2019-12-06
Dell Command Configure versions prior to 4.2.1 contain an uncontrolled search path vulnerability. A locally authenticated malicious user could exploit this vulnerability by creating a symlink to a target file, allowing the attacker to overwrite or corrupt a specified file on the system.
CVE-2019-11293
PUBLISHED: 2019-12-06
Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter. A remote authenticated malicious user could gain access to user credentials via the uaa.log file if authentication is provided via query parameters.
CVE-2019-16771
PUBLISHED: 2019-12-06
Versions of Armeria 0.85.0 through and including 0.96.0 are vulnerable to HTTP response splitting, which allows remote attackers to inject arbitrary HTTP headers via CRLF sequences when unsanitized data is used to populate the headers of an HTTP response. This vulnerability has been patched in 0.97....
CVE-2019-1551
PUBLISHED: 2019-12-06
There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are n...
CVE-2019-16671
PUBLISHED: 2019-12-06
An issue was discovered on Weidmueller IE-SW-VL05M 3.6.6 Build 16102415, IE-SW-VL08MT 3.5.2 Build 16102415, and IE-SW-PL10M 3.3.16 Build 16102416 devices. Remote authenticated users can crash a device with a special packet because of Uncontrolled Resource Consumption.