Slapper variants pose minor threat

Article

Slapper variants pose minor threat

Two variants of the Slapper worm have surfaced thanks to its source code being widely distributed, virus experts say.

The two variants of Slapper, dubbed Slapper.B and Slapper.C, were discovered early this week. The variants are also called "Cinik" and "Unlock," after the file names the worms employ.

FOR MORE SLAPPER INFORMATION

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

"Slapper worm exploits OpenSSL hole, sets up P2P network"

"OpenSSL overflowing with buffer problems"

CERT advisory on the worm (includes links to OpenSSL patches)


Feedback on this story? Send your comments to News Writer Edward Hurley

The new worms, however, don't pose much of a security risk because they exploit the same vulnerability as the original Slapper worm. Users who employed workarounds or patched their systems are safe from the variants. Yet the variants could signify the beginning of new worms spawned from the Slapper source code.

The original worm -- Slapper.A, as it's commonly known -- reared its head a week ago, targeting a vulnerability in versions of OpenSSL running on Linux-based Apache Web servers. The worm takes advantage of a buffer overflow vulnerability in the open-source version of Secure Sockets Layer, a method for creating secured HTTP connections.

After infecting a machine, the worm tries to connect to a peer-to-peer network and could enable a denial of service attack.

The new worms technically aren't more hazardous than the original, said Dan Ingevaldson, team lead for Atlanta-based Internet Security Systems' X-Force R&D. Bugs weren't fixed in the code. Significant new functionality wasn't added.

Though it's impossible to tell, it's unlikely that the worm variants were released by the author of Slapper.A, said Mikael Albrecht, product manager for antivirus solutions at Helsinki, Finland-based F-Secure, since "only minor adjustments were made before being released again."

The variants, however, use different ports to connect to the back door of the system created by the original worm. Slapper.B uses port 1978 to connect to the back door rather than port 2002, which Slapper.A used. Slapper.C uses port 4156.

They also include a "mailme()" function, which e-mails the IP address and hostname of the infected system back to an e-mail address most likely controlled by the writer.

The mere existence of Slapper.B and Slapper.C is not as worrisome as the fact that someone reused the source code so quickly. Ingevaldson predicts other worms will be written using the Slapper code and will perhaps take advantage of other vulnerabilities . The Slapper's ability to create a peer-to-peer network combined with new automatic attack tools could make for a dangerous combination, he said.

Albrecht agrees that it's very likely that the code for Slapper will resurface in some form.

"We saw the same thing in '95 when macro viruses began appearing. The source code was available, so we saw a huge amount of copycats," he said.

Moreover, Ingevaldson rejects the argument that having the source code available will make fighting future worms easier.

"Reverse engineering worms is pretty easy. We can do it quickly," he said. "The dangers of having the source code available severely outweigh any potential benefits."