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
How the US Chooses Which Zero-Day Vulnerabilities to Stockpile
Newest First  |  Oldest First  |  Threaded View
MelBrandle
50%
50%
MelBrandle,
User Rank: Moderator
1/26/2019 | 2:33:26 AM
Selective disclosure
What I reckon is happening is that the government is keeping all these secrets in storage for fear that if the data got out, that the hackers would be able to replicate what's been going on. They would have to be very careful what  information to release if they're going to disclose any of it at all!
michaelmaloney
50%
50%
michaelmaloney,
User Rank: Apprentice
1/25/2019 | 2:27:16 AM
Staying neutral is best
I guess the I belong in the third group as well because every scenario would often come with its own pros and cons. It is not entirely up to us alone to weigh in on whether or not the vulnerabilities should indeed be kept in a secret storage or be let out in the open. Instead, we need to analyze on the given situation at that exact moment in time to see which solution suits best.
ConwayK9781
100%
0%
ConwayK9781,
User Rank: Strategist
1/17/2019 | 9:19:02 AM
Huh...
> "And then there's a third group, to which I belong. This crowd understands both the benefits and consequences that can occur when governments find and conceal vulnerabilities."
> implies only third group understand both
> proceeds to show that the third group clearly doesn't, as they support a government weaponizing zero-days at the expense of the citizens for its own personal gain




Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. 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-2020-10595
PUBLISHED: 2020-03-31
pam-krb5 before 4.9 has a buffer overflow that might cause remote code execution in situations involving supplemental prompting by a Kerberos library. It may overflow a buffer provided by the underlying Kerberos library by a single '\0' byte if an attacker responds to a prompt with an answer of a ca...
CVE-2020-11414
PUBLISHED: 2020-03-31
An issue was discovered in Progress Telerik UI for Silverlight before 2020.1.330. The RadUploadHandler class in RadUpload for Silverlight expects a web request that provides the file location of the uploading file along with a few other parameters. The uploading file location should be inside the di...
CVE-2020-11111
PUBLISHED: 2020-03-31
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.activemq.* (aka activemq-jms, activemq-core, activemq-pool, and activemq-pool-jms).
CVE-2020-11112
PUBLISHED: 2020-03-31
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.commons.proxy.provider.remoting.RmiProvider (aka apache/commons-proxy).
CVE-2020-11113
PUBLISHED: 2020-03-31
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.openjpa.ee.WASRegistryManagedRuntime (aka openjpa).