Security Threat Or False Alarm?

Improper programming around a little-known but ubiquitous communication protocol used in networking gear, Abstract Syntax Notation One, or ASN.1, has the government, networking manufacturers, security researchers, and IT executives worried that networks--including key parts of the Internet, phone systems, and the electrical power grid--may be vulnerable to disruptive buffer overflow and malformed packet attacks.

The problem, made public last week, was first identified in February when Internet security watch group CERT Coordination Center disclosed products vulnerable to attack because of a weakness in the Simple Network Management Protocol, in which ASN.1 is widely used. The fallout from the ASN.1 problem may especially threaten electric utilities, which rely on ASN.1 throughout their power grids. "That includes power grids for nuclear power generators,'' says Michael Erbschloe, VP of research at research firm Computer Economics.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"We don't know the scope of the problem," says a network administrator at a major electric utility. "We installed a lot of equipment that runs ASN.1 when we did our Y2K work."

Lucent Technologies Inc. says it's identifying which of its products depend on ASN.1. But Cisco Systems is waiting for more information. Right now, it's like "looking for a needle in a haystack," says Mike Caudill, a product security incident response manager at Cisco. That worries the chief security officer at a large insurance company, who says, "I'd rather Cisco find any potential problems in their equipment before some hacker group."


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links