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.

Vulnerabilities / Threats

1/12/2009
01:46 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

IRS Security Holes Leave Taxpayer Data At Risk, GAO Says

New report highlights lingering security weaknesses in the Internal Revenue Service's network and systems

Just in time for tax season: The Internal Revenue Service (IRS) is under fire again for failing to take the necessary steps needed to prevent security breaches targeting sensitive taxpayer information.

A new Government Accountability Office (GAO) report (PDF) says the IRS still has not addressed most security weaknesses previously highlighted in past audits by the watchdog agency.

The GAO has advised IRS commissioner Douglas Shulman to deploy an agencywide security program, and has provided the IRS with recommendations on how to correct the outstanding security weaknesses in the agency's network and systems infrastructure. The GAO's findings are based on an audit conducted between April 2008 and January 2009.

One big hole: The IRS still allows any user on its internal network to get IDs and passwords for mission-critical applications even if his job doesn't require it, leaving the door open for abuse, according to the GAO.

"Despite IRS' progress, information security control weaknesses continue to jeopardize the confidentiality, integrity, and availability of financial and sensitive taxpayer information. IRS did not consistently implement controls that were intended to prevent, limit, and detect unauthorized access to its systems and information," the report says.

Among the security woes documented in the GAO report: The IRS didn't always enforce strong passwords, and it didn't ensure that only authorized users access applications. The agency also did not consistently encrypt some sensitive data, nor did it "effectively" monitor changes on its mainframe or protect is computer resources "physically."

The IRS still transmits data unencrypted from its financial accounting system, for instance, according to the GAO.

The GAO says the main reason the IRS still hasn't corrected these security weaknesses is that it has not yet implemented an agencywide security program. "Specifically, IRS did not annually review risk assessments for certain systems, comprehensively test for certain controls, or always validate the effectiveness of remedial actions," the GAO report says. "Until these weaknesses are corrected, the agency remains particularly vulnerable to insider threats, and IRS is at increased risk of unauthorized access to and disclosure, modification, or destruction of financial and taxpayer information, as well as inadvertent or deliberate disruption of system."

Some good news, however, did emerge from the GAO report: The IRS has fixed 49 of 115 problems cited by the GAO in previous audits, including implementing controls for unauthenticated network access and user IDs on the mainframe, encrypting sensitive data that travels over its network, improving vulnerability patching, and updating its contingency plans.

According to the GAO, the IRS' Shulman said the IRS is committed to locking down security on its systems and will create an action plan to address each of the GAO's recommendations.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-20092
PUBLISHED: 2021-05-13
File Upload vulnerability exists in ArticleCMS 1.0 via the image upload feature at /admin by changing the Content-Type to image/jpeg and placing PHP code after the JPEG data, which could let a remote malicious user execute arbitrary PHP code.
CVE-2020-21342
PUBLISHED: 2021-05-13
Insecure permissions issue in zzcms 201910 via the reset any user password in /one/getpassword.php.
CVE-2020-25713
PUBLISHED: 2021-05-13
A malformed input file can lead to a segfault due to an out of bounds array access in raptor_xml_writer_start_element_common.
CVE-2020-27823
PUBLISHED: 2021-05-13
A flaw was found in OpenJPEG’s encoder. This flaw allows an attacker to pass specially crafted x,y offset input to OpenJPEG to use during encoding. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.
CVE-2020-27830
PUBLISHED: 2021-05-13
A vulnerability was found in Linux Kernel where in the spk_ttyio_receive_buf2() function, it would dereference spk_ttyio_synth without checking whether it is NULL or not, and may lead to a NULL-ptr deref crash.