Risk //

Compliance

2/28/2018
02:30 PM
50%
50%

FTC Settles with Venmo on Security Allegations

Proposed settlement addresses complaints that Venmo misrepresented its security and privacy features.

The Federal Trade Commission has reached a settlement with Venmo, a PayPal company, regarding allegations that the company misrepresented the way it handled and made available funds as well as the level of security of its financial platform.

The charges, originally filed in 2015, alleged that some Venmo customers suffered "real harm" when the company either didn't make funds available in the advertised time or withdrew funds after their initial deposit.

Venmo advertised "bank-grade security" and transaction privacy for their customers; the FTC found that the company had delivered neither. In the proposed settlement, Venmo admits to no wrongdoing, but does admit to the facts of the allegations.

Under the agreement, approved by a 2-0 vote of the commission, Venmo is required to stop mis-representing the level of security available for transactions and to be more transparent with customers about both the security and privacy of their transactions. In addition, because of the GLB component of the complaint and settlement, Venmo will have to submit to twice-annual audits of its compliance for 10 years.

The proposed agreement will be published to the Federal Register and become subject to public comment for 30 days. After that time, the commission will vote on whether or not the settlement will become final.

Read more here and here.
 

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Microsoft Fixes 11 Critical, 39 Important Vulns
Kelly Sheridan, Staff Editor, Dark Reading,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1060
PUBLISHED: 2018-06-18
python before versions 2.7.15, 3.4.9, 3.5.6 and 3.7.0 is vulnerable to catastrophic backtracking in pop3lib's apop() method. An attacker could use this flaw to cause denial of service.
CVE-2018-1090
PUBLISHED: 2018-06-18
In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with API access can then view these secrets.
CVE-2018-1152
PUBLISHED: 2018-06-18
libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.
CVE-2018-1153
PUBLISHED: 2018-06-18
Burp Suite Community Edition 1.7.32 and 1.7.33 fail to validate the server certificate in a couple of HTTPS requests which allows a man in the middle to modify or view traffic.
CVE-2018-12530
PUBLISHED: 2018-06-18
An issue was discovered in MetInfo 6.0.0. admin/app/batch/csvup.php allows remote attackers to delete arbitrary files via a flienamecsv=../ directory traversal. This can be exploited via CSRF.