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.

Attacks/Breaches

6/28/2007
07:35 AM
50%
50%

Not One Size Fits All

One man's firewall is another man's kludge

3:35 PM -- Sometimes, what's good for one application just isn't good for another.

I've been in the game for a long time and get to see a lot of interesting tactics to prevent exploitation. Recently, I've been involved in auditing a software application, and one of the interesting aspects is how security theory varies from one technology to another.

With Websites, for instance, one of the reasons firewalls have proven to be fairly overkill is because often attackers are coming from addresses where many other people are also originating from (through network address translation). So you can't simply block by an IP address -- yet you feel you must block by them because you are getting attacked by an IP address.

Now look at software. If software running on your desktop detects that someone is attempting to do something malicious, it may be OK to block the request completely -- unlike with a firewall. Who cares if it breaks for a single instance of a single Web page? It's far better than having your local machine compromised. Rather than attempting to handle an error, let your application fail in a safe way. When the system starts acting responsibly again, your application can start running again in a sane way.

While the network can cause major outages if it fails, the worst that a local process can do is cause you to reboot. Setting up a denial-of-service situation on the desktop affects one user temporarily, whereas on the network, tens of thousands of users, as in the case of AOL's proxies.

One is acceptable; the other can be a significant detriment to your business. Different security people work on different systems and with different paradigms, so remember that one security professional's advice on blocking exploits does not fit all circumstances, especially if they aren't working in the same industry you are.

— RSnake is a red-blooded lumberjack whose rants can also be found at Ha.ckers and F*the.net. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19767
PUBLISHED: 2019-12-12
The Linux kernel before 5.4.2 mishandles ext4_expand_extra_isize, as demonstrated by use-after-free errors in __ext4_expand_extra_isize and ext4_xattr_set_entry, related to fs/ext4/inode.c and fs/ext4/super.c, aka CID-4ea99936a163.
CVE-2019-19768
PUBLISHED: 2019-12-12
In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer).
CVE-2019-19769
PUBLISHED: 2019-12-12
In the Linux kernel 5.3.10, there is a use-after-free (read) in the perf_trace_lock_acquire function (related to include/trace/events/lock.h).
CVE-2019-19770
PUBLISHED: 2019-12-12
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file).
CVE-2019-19771
PUBLISHED: 2019-12-12
The lodahs package 0.0.1 for Node.js is a Trojan horse, and may have been installed by persons who mistyped the lodash package name. In particular, the Trojan horse finds and exfiltrates cryptocurrency wallets.