Commentary

Content posted in September 2006
Quick, Encrypt Everything!
Commentary  |  9/22/2006  | 
On the surface, it seems like a good idea. Convert all your corporate information into a form unreadable by anyone except the intended recipient. Very straightforward and not terribly difficult to do. But there's a dark side to encryption. Just like anesthesiologists like to joke that putting you under is free, it's waking you up that costs so much money, decrypting your data is the part of the process where things get hairy. In this era of epidemically stolen and lost laptops and mobile devices
Spinach Woes Portend Repercussions Of Cyberattack
Commentary  |  9/19/2006  | 
Wonder what the aftereffect of a terrorist attack on the Internet would look like? The way we're responding to contaminated spinach provides a clue.
Data Protection: It Doesn't Get Any Better Than This
Commentary  |  9/13/2006  | 
Corporate America's efforts at data protection--in particular, protecting sensitive personal information about customers--have in many cases failed miserably. There's a long and dubious list of data breaches, losses, thefts, and mishandlings from the past 20 months, with the total number of records containing sensitive personal information involved in security breaches now topping 93 million. Time and again, we've taken to task
HP Must Rebuild The Damage To Its Image
Commentary  |  9/11/2006  | 
Like most everyone, I've been thinking about the victims of Sept. 11, 2001, in the past few days. I'm also remembering former Hewlett-Packard Chairman Lew Platt, who died on Sept. 8 of last year, as his former company faces a criminal investigation into tactics used to hunt down the source of media leaks.
Post 9/11: Five Years Of IT Promise And Failure
Commentary  |  9/8/2006  | 
Sept. 11, 2001, spurred IT innovation and integration like no other event in history. Driven by fear, defiance, and inspiration, industry and government quickly promised to correct the conditions--including siloed data repositories, incompatible communications systems, and lax security practices--that allowed the terrorist attacks to be executed with such deadly precision. How far have we come in five years? Let's put it this way: We've got a long way to go.
Airing Dirty Security Laundry
Commentary  |  9/5/2006  | 
We all need to be smart, stay informed, and understand our systems well enough to figure out what needs fixing first, or risk being out of business. No vendor, well-intentioned or not, can make these decisions for us; we need to take this responsibility for ourselves.


'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12630
PUBLISHED: 2018-06-21
NEWMARK (aka New Mark) NMCMS 2.1 allows SQL Injection via the sect_id parameter to the /catalog URI.
CVE-2018-12631
PUBLISHED: 2018-06-21
Redatam7 (formerly Redatam WebServer) allows remote attackers to read arbitrary files via /redbin/rpwebutilities.exe/text?LFN=../ directory traversal.
CVE-2018-12632
PUBLISHED: 2018-06-21
Redatam7 (formerly Redatam WebServer) allows remote attackers to discover the installation path via an invalid LFN parameter to the /redbin/rpwebutilities.exe/text URI.
CVE-2018-12581
PUBLISHED: 2018-06-21
An issue was discovered in js/designer/move.js in phpMyAdmin before 4.8.2. A Cross-Site Scripting vulnerability has been found where an attacker can use a crafted database name to trigger an XSS attack when that database is referenced from the Designer feature.
CVE-2018-12613
PUBLISHED: 2018-06-21
An issue was discovered in phpMyAdmin 4.8.x before 4.8.2, in which an attacker can include (view and potentially execute) files on the server. The vulnerability comes from a portion of code where pages are redirected and loaded within phpMyAdmin, and an improper test for whitelisted pages. An attack...