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.


10:50 AM
Connect Directly

Researchers Thankful for New Paypal Policy

Immunity from legal action for researchers who follow site's responsible disclosure procedures

It may be the protection and peace of mind that Web application security researchers have been waiting for: PayPal's new vulnerability disclosure policy states that the company won't take any legal action against a researcher who properly follows its procedure for reporting bugs in its software. (See Laws Threaten Security Researchers).

"I would certainly hope it's the start of a trend," says Jeremiah Grossman, CTO and founder of WhiteHat Security, who blogged on this development late yesterday. Grossman says there have been other signs of hope lately as well for freeing Web app security researchers to do their work without the worry of legal implications: a Microsoft panelist last week at the OWASP and Web Application Security AppSec 2007 Conference said the company wouldn't take action against anyone who finds bugs in its Websites. "But Microsoft has not gone so far as to document that publicly like PayPal," Grossman says.

Web application security researchers don't have the freedoms of other security researchers, who for the most part work unrestricted in their efforts to search for bugs in operating systems, device drivers, or other apps via their own machines. Computer security laws make looking for vulnerabilities on live Web servers dangerous legal territory, and the laws aimed at protecting companies from attackers have also inadvertently hurt researchers in this space.

Grossman says PayPal's policy may well be the first to guarantee Web researchers protection when they responsibly report a vulnerability to the company. PayPal's policy says, in part: "To encourage responsible disclosure, we commit that -- if we conclude that a disclosure respects and meets all the guidelines outlined below -- we will not bring a private action or refer a matter for public inquiry."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • WhiteHat Security
  • Microsoft Corp. (Nasdaq: MSFT) Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 5/28/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: Can you smell me now?
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    PUBLISHED: 2020-05-29
    There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
    PUBLISHED: 2020-05-29
    A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
    PUBLISHED: 2020-05-29
    All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.