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
Duqu Malware: Still No Patch
Threaded  |  Newest First  |  Oldest First
jrapoza
50%
50%
jrapoza,
User Rank: Apprentice
11/2/2011 | 11:10:56 PM
re: Duqu Malware: Still No Patch
This is just another good example of why it was a really bad idea to allow scripting and code execution from documents. There was really no need for that and it caused many security headaches.

Jim Rapoza is an InformationWeek Contributing Editor
Bprince
50%
50%
Bprince,
User Rank: Ninja
11/4/2011 | 2:02:48 AM
re: Duqu Malware: Still No Patch
MS issued information about a workaround earlier tonight.
http://technet.microsoft.com/e...
Brian Prince, InformationWeek/DarkReading Comment Moderation
YMOM100
50%
50%
YMOM100,
User Rank: Apprentice
11/5/2011 | 3:55:28 PM
re: Duqu Malware: Still No Patch
How come that a document can take down an entire system? Why would Word need direct access to kernel resources in the first place? This is not just a mistake in coding, the entire design is flawed.
kjh..2
50%
50%
kjh..2,
User Rank: Apprentice
11/6/2011 | 12:39:20 PM
re: Duqu Malware: Still No Patch
Isn't DuQu exploiting a vulnerability in TrueType Font Processing ?

IIRC, Font Processing has been embedded in the NT Kernel since NT-4 for performance reasons.

Why would that be necessary any more given the raw power of today's hardware is up for discussion.

MS's design decisions (? or were they marketing decisions ?) as to what should and should not be included in Kernel-Level Code continue to bite them again and again.

-- kjh


COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/7/2020
The Coronavirus & Cybersecurity: 3 Areas of Exploitation
Robert R. Ackerman Jr., Founder & Managing Director, Allegis Capital,  4/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20637
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connecti...
CVE-2020-11650
PUBLISHED: 2020-04-08
An issue was discovered in iXsystems FreeNAS 11.2 and 11.3 before 11.3-U1. It allows a denial of service.
CVE-2020-11653
PUBLISHED: 2020-04-08
An issue was discovered in Varnish Cache before 6.0.6 LTS, 6.1.x and 6.2.x before 6.2.3, and 6.3.x before 6.3.2. It occurs when communication with a TLS termination proxy uses PROXY version 2. There can be an assertion failure and daemon restart, which causes a performance loss.
CVE-2020-2732
PUBLISHED: 2020-04-08
A flaw was discovered in the way that the KVM hypervisor handled instruction emulation for an L2 guest when nested virtualisation is enabled. Under some circumstances, an L2 guest may trick the L0 guest into accessing sensitive L1 resources that should be inaccessible to the L2 guest.
CVE-2020-1627
PUBLISHED: 2020-04-08
A vulnerability in Juniper Networks Junos OS on vMX and MX150 devices may allow an attacker to cause a Denial of Service (DoS) by sending specific packets requiring special processing in microcode that the flow cache can't handle, causing the riot forwarding daemon to crash. By continuously sending ...