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
2 Million Fake Net Neutrality Comments Stole American Identities
Oldest First  |  Newest First  |  Threaded View
SchemaCzar
50%
50%
SchemaCzar,
User Rank: Strategist
12/15/2017 | 9:17:28 AM
Ratio of "pro" to "con" fake posts could suggest unseen economic or political motives
Schneiderman's office did a valuable service.  Now this is definitely one of the more useless ways of gauging public opinion - no real authenticated identity to canvass citizens?  

However, the question I have is what is the ratio pro/con of fake comments?  If we see one side or the other exerting money and effort to swing the decision, it may lead us to hidden consequences of rescinding or preserving net neutrality that would give us further information in this important debate.

It's sort of disappointing that Schneiderman did not reveal this ratio.
gruntsters
50%
50%
gruntsters,
User Rank: Strategist
12/15/2017 | 11:35:21 AM
Re: Ratio of "pro" to "con" fake posts could suggest unseen economic or political motives
I agree. Which way did the 2 million accounts lean? Why hasn't the NY AG listed this information?
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
12/15/2017 | 3:41:25 PM
Re: Ratio of "pro" to "con" fake posts could suggest unseen economic or political motives
As a past resident of NY State, I have many reasons to hate ALBANY and all that goes on there.  BUT ONE WORD OF GREAT ADVICE ----- IF you have or had relatives in the state, checked UNCLAIMED FUNDS ---- We came away with a substantial chunk of unknown change in the XX,XXX.xx number range. 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/18/2017 | 7:09:16 PM
Addresses of commenters
WTH?

I'm really concerned how much of these comments are a matter of public record. People's names and addresses are often enough to commit identity theft.

Of course, the same goes for most voting records.

It's a shame, really.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-45340
PUBLISHED: 2022-01-25
In Libsixel prior to and including v1.10.3, a NULL pointer dereference in the stb_image.h component of libsixel allows attackers to cause a denial of service (DOS) via a crafted PICT file.
CVE-2021-45341
PUBLISHED: 2022-01-25
A buffer overflow vulnerability in CDataMoji of the jwwlib component of LibreCAD 2.2.0-rc3 and older allows an attacker to achieve Remote Code Execution using a crafted JWW document.
CVE-2022-0268
PUBLISHED: 2022-01-25
Cross-site Scripting (XSS) - Stored in Packagist getgrav/grav prior to 1.7.28.
CVE-2022-0338
PUBLISHED: 2022-01-25
Improper Privilege Management in Conda loguru prior to 0.5.3.
CVE-2022-23935
PUBLISHED: 2022-01-25
lib/Image/ExifTool.pm in ExifTool before 12.38 mishandles a $file =~ /\|$/ check.