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
The Staggering Complexity of Application Security
Newest First  |  Oldest First  |  Threaded View
af_bugcrowd
af_bugcrowd,
User Rank: Author
11/12/2014 | 6:31:52 PM
Re: Devils you know
It's only going to be worse in mobile vulnerabilities once the eyeballs and money on them catches up to usage. There are so many different devices that are going to be unique creases in many of them.  
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
11/11/2014 | 9:39:44 AM
Re: Devils you know
@Stratustician It's hard for me to imagine that DevOps can still be so tone deaf when it comes to appsec when vulnerabilities like Heartbleed and POODLE have become so commonplace in security news reports. 
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
11/10/2014 | 3:43:24 PM
Re: What can you control?
It's  hard for me to imagine getting 100 percent compliance with anything. So anything that moves the needle in the right direction would seem to make sense to me..
TerryB
TerryB,
User Rank: Ninja
11/10/2014 | 1:27:34 PM
What can you control?
Great article and insight. But doesn't this only work if EVERYONE in the stack does it? Your testing may show that your product is fine but holes in o/s or browser still expose you. Maybe I'm just naive but were the old mainframes running MVS-370 as vulnerable as Windows/browser you run apps on today?
Stratustician
Stratustician,
User Rank: Moderator
11/10/2014 | 1:27:02 PM
Re: Devils you know
So true.  For me I find it's usually one of 2 issues that cause these security issues. Often DevOps teams don't have good security input early enough in the design stage, or don't keep up with testing prior to release. The other option is they bring security in way too late and then plug their ears when vulnerabilities in the code are detected by the security team after release, and then it's much harder to pull the app or change it without causing downtime. 

That or overall folks just don't feel that app security is that important to the overall security posture of an organization, which sadly is why we might be in this position in the first place.
Whoopty
Whoopty,
User Rank: Ninja
11/10/2014 | 12:19:33 PM
Devils you know
I know a few people who do a little freelance tech security work and several of them have pointed out major bugs to corporations about their sites or apps and often times, the flaw isn't fixed because it would require such an upheavel. It's worrying and makes you wonder when a big breach occurs, whether the company knew about it and chose to do nothing.

The delemna of course is that those firms will be damned if they interrupt service for a fix, and damned if they get caught out later. It's a difficult situation to be in. 


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-29248
PUBLISHED: 2022-05-25
Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains a vulnerability with the cookie middleware. The vulnerability is that it is not checked if the cookie domain equals the domain of the server which sets the cookie via the Set-Cookie header, allowing a malicious server to ...
CVE-2022-29402
PUBLISHED: 2022-05-25
TP-Link TL-WR840N EU v6.20 was discovered to contain insecure protections for its UART console. This vulnerability allows attackers to connect to the UART port via a serial connection and execute commands as the root user without authentication.
CVE-2021-27783
PUBLISHED: 2022-05-25
User generated PPKG file for Bulk Enroll may have unencrypted sensitive information exposed.
CVE-2021-27779
PUBLISHED: 2022-05-25
VersionVault Express exposes sensitive information that an attacker can use to impersonate the server or eavesdrop on communications with the server.
CVE-2021-44719
PUBLISHED: 2022-05-25
Docker Desktop 4.3.0 has Incorrect Access Control.