Comments
How Guccifer 2.0 Got 'Punk'd' by a Security Researcher
Newest First  |  Oldest First  |  Threaded View
antivirussupport12
50%
50%
antivirussupport12,
User Rank: Guru
3/12/2018 | 11:46:13 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
I totally agree with you.This the way we can tackle this situation.if you know the situation and all other prospects you can handle it in a better way. visit https://antivirussupport.org for more.
ellascottgm123
50%
50%
ellascottgm123,
User Rank: Apprentice
3/11/2018 | 10:07:03 PM
Re: Why would anyone still believe Guccifer was driven by Russians?
Such a very useful article. Very interesting to read this article.I would like to thank you for the efforts you had made for writing this awesome article.
Gorilla Hunter
67%
33%
Gorilla Hunter,
User Rank: Strategist
3/9/2018 | 10:21:49 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
So because he stopped talking to a reporter, he was punked? You demand facts, yet you are unable to back up your claim with any of your own. Julian Assange, the publisher of the hacked emails and knows who the source is, has came out time and time again saying the Russians had nothing to do with it.

http://thehill.com/policy/cybersecurity/346904-assange-meets-us-congressman-vows-to-prove-russia-did-not-leak-him

https://www.democracynow.org/2017/4/12/full_interview_julian_assange_on_trump 

https://www.huffingtonpost.com/entry/donna-brazile-owes-an-apology-to-julian-assange-and_us_59fe1c3ae4b076eaaae2701d

I doubt the story because I looked at the authors twitter feed, saw her politics, and then read her parroting the same agenda, and  once again hear the clams of "Russia did hax", when everyone who is involved with the DNC email dump says otherwise.  Also included three sources from both left and right. But hey, a dude stopped talking to a reporter, ao case closed, right?

 
Dong_Johnson
50%
50%
Dong_Johnson,
User Rank: Apprentice
3/8/2018 | 1:38:07 PM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
You're not understanding the article I guess.  It's pretty clear Gucci was punked because he's no longer responding.  

 

Russia has various means of accomplishing what they want to, and using low-level useful idiots isn't below their means either.  I agree with the premise presented in the article that it's clear Russia wasn't going "all-in" using state resources (which would be attributable directly, of issue) to publish the stolen emails, and instead decided to disseminate them using troll networks rather than official ones.  The fact is you have no compelling or offered reason to doubt anything in this story.  If you did you wouldn't be doing the typical spambot/chatbot song and dance of crying about people focusing on "russia russia russia' for what Russia did did did provably provably provably.  Get your politics out of here, this is a discussion about facts.   The fact is Russia was involved.

Once again, if you want to discredit any aspect of this, you're going to need something to point to.  Whining won't help your case.
Gorilla Hunter
40%
60%
Gorilla Hunter,
User Rank: Strategist
3/8/2018 | 11:02:48 AM
Re: Why would anyone still believe Guccifer was driven by Russians?
Because "RUSSIA, RUSSIA, RUSSIA". There is nothing here that shows that Guccifer was "punked" or that he is even connected to the Russians, but we have to hear once again "RUSSIA, RUSSIA, RUSSIA!!!1!"
SchemaCzar
50%
50%
SchemaCzar,
User Rank: Strategist
3/8/2018 | 10:18:09 AM
Why would anyone still believe Guccifer was driven by Russians?
Everything in this article makes me doubt that Guccifer 2.0 was driven by Russian state actors.  To fall for a trick like this is not what happens with Russian state-level hackers.  If the Russians were paying him/her, the only purpose was to muddy the waters.  It's hard to think of a nation-state, or a trans-national movement, that would be unable to set up a cutout like this to "look Russian."


WebAuthn, FIDO2 Infuse Browsers, Platforms with Strong Authentication
John Fontana, Standards & Identity Analyst, Yubico,  9/19/2018
Turn the NIST Cybersecurity Framework into Reality: 5 Steps
Mukul Kumar & Anupam Sahai, CISO & VP of Cyber Practice and VP Product Management, Cavirin Systems,  9/20/2018
NSS Labs Files Antitrust Suit Against Symantec, CrowdStrike, ESET, AMTSO
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "I'm not sure I like this top down management approach!"
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-17332
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. The svgGetNextPathField function in svg_string.c returns its input pointer in certain circumstances, which might result in a memory leak caused by wasteful malloc calls.
CVE-2018-17333
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. A stack-based buffer overflow in svgStringToLength in svg_types.c allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because sscanf is misused.
CVE-2018-17334
PUBLISHED: 2018-09-22
An issue was discovered in libsvg2 through 2012-10-19. A stack-based buffer overflow in the svgGetNextPathField function in svg_string.c allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact because a strncpy copy limit is miscalculated.
CVE-2018-17336
PUBLISHED: 2018-09-22
UDisks 2.8.0 has a format string vulnerability in udisks_log in udiskslogging.c, allowing attackers to obtain sensitive information (stack contents), cause a denial of service (memory corruption), or possibly have unspecified other impact via a malformed filesystem label, as demonstrated by %d or %n...
CVE-2018-17321
PUBLISHED: 2018-09-22
An issue was discovered in SeaCMS 6.64. XSS exists in admin_datarelate.php via the time or maxHit parameter in a dorandomset action.