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
XSS Flaw In TweetDeck Leads To Spread Of Potential Exploits
Newest First  |  Oldest First  |  Threaded View
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
6/12/2014 | 12:00:36 PM
Browser Alternatives - Safe?
Some mention has been made of trying alternatives to the usual suspects of the web browser world (hardened Lynx (text only), WhiteHat Aviator), but let's not forget that not all web traffice goes across a browser - many applications act like web browsers on the inside and are just as exploitable through methods like XSS.  This is especially true with desktops like GNOME where just about every app I use tugs on Mozilla APIs or similar.  As long as the key web elements are there XSS can still work on the client-side as if you were using a browser.  I
mention this only because users shouldn't think because they turn to other apps to access TweetDeck they are safe.
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
6/12/2014 | 11:44:19 AM
Surprised
I was pretty surprised Tweetdeck got caught out by this to be honest. It's large enough and has been operating long enough that you'd think it would have some solid people in place to ward off problems like this.

That said, I did hear that it was to do with the heart symbol which hasn't been around long, so it was a relatively recent exploit it seems. 
Randy Naramore
50%
50%
Randy Naramore,
User Rank: Ninja
6/12/2014 | 11:08:13 AM
Re: XSS Flaw in TweetDeck
Maybe the major retailers will learn from these incidents but you would think the Target would have been a wakeup call for all.
Robert McDougal
50%
50%
Robert McDougal,
User Rank: Ninja
6/12/2014 | 11:01:07 AM
Re: XSS Flaw in TweetDeck
Exactly correct Randy!  This is yet another example where putting secure coding first and foremost would prevent a major issue.
Randy Naramore
50%
50%
Randy Naramore,
User Rank: Ninja
6/12/2014 | 9:04:58 AM
XSS Flaw in TweetDeck
Another example of how secure coding can help all. The use of "white lists" in code can eliminate this exploit from occurring. White lists are used to only allow certain characters to be inputed into form fields and not allow characters that are normally part of XSS attacks. OWASP has information to help with this.

https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet#A_Positive_XSS_Prevention_Model

 


Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.
CVE-2021-32553
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-17 package apport hooks, it could expose private data to other local users.
CVE-2021-32554
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the xorg package apport hooks, it could expose private data to other local users.