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.

Infrastructure Security //

DNS

12/12/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

'Novidade' Exploit Changes DNS Settings in Home & Small Business Routers

Trend Micro has picked up on a new exploit dubbed 'Novidade,' which targets small business and home routers and changes their DNS settings to redirect the traffic as part of an attack.

A new exploit spotted by Trend Micro is designed to target small home and office (SOHO) routers, as well as consumer-grade home routers, by changing their internal domain name service (DNS) setting to one that is determined by the attacker.

Trend researchers note that this exploit is effected using the cross-site request forgery (CSRF) method.

Once the malicious DNS has been installed, the router becomes part of a "pharming" attack. This kind of attack will redirect website traffic from all the devices connected to the same router by resolving targeted domains to the IP address of their server.

Trend named the exploit kit Novidade -- "novelty" in Portuguese -- due to the title string "Novidade!" on the web pages of all the current variants of it.

Novidade infection chain\r\n(Source: Trend Micro)\r\n
Novidade infection chain
\r\n(Source: Trend Micro)\r\n

Novidade was found to be delivered through differing methods include malvertising, compromised website injection, and instant messengers. The user needs to click on a link to activate the first steps of the attack.

The first thing the malicious URL in the link does is to try HTTP requests to common local IP address that are mostly used by routers. Should a connection be successfully established, Novidade will query the detected IP address to download a corresponding exploit payload, encoded in Base64. It will then try and log into the router with a set of default account names and passwords, after which a CSRF attack is attempted that can actually change the DNS settings.

After that change, if -- for example -- a user tries to connect to a targeted bank domain the injected DNS server could resolve the request to an IP address that hosts a fake banking website.

Trend researchers has found three variants of Novidade, and they all have similar attack operations. The first version was the most basic of the group, and was seen in the wild in August 2017.

The second variant adds a runtime JavaScript obfuscator which will make the landing page take different forms depending on the attack.

Finally, Trend saw that the third variant was still retaining the JavaScript obfuscator to refine the code on the landing page. At the same time, however, it added a new feature to retrieve the victim's local IP address by making requests to STUN servers with WebRTC.

Also, the third variant embedded a shortened URL link on the Novidade landing page. This is not used for redirection efforts but tracks attack statistics.

In its report, Trend researchers identify the following list of routers, which they admit is not all inclusive, that are being targeted by the attack.

This list includes:

  • A-Link WL54AP3 / WL54AP2
  • D-Link DSL-2740R
  • D-Link DIR 905L
  • Medialink MWN-WAPR300
  • Motorola SBG6580
  • Realtron
  • Roteador GWR-120
  • Secutech RiS-11/RiS-22/RiS-33
  • TP-Link TL-WR340G / TL-WR340GD
  • TP-Link WR1043ND V1

Trend recommends changing the router's default IP address, as well as disabling remote access features, which will minimize the chances for an attacker to externally manipulate the device.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-24360
PUBLISHED: 2021-06-14
The Yes/No Chart WordPress plugin before 1.0.12 did not sanitise its sid shortcode parameter before using it in a SQL statement, allowing medium privilege users (contributor+) to perform Blind SQL Injection attacks
CVE-2021-24382
PUBLISHED: 2021-06-14
The Smart Slider 3 Free and pro WordPress plugins before 3.5.0.9 did not sanitise the Project Name before outputting it back in the page, leading to a Stored Cross-Site Scripting issue. By default, only administrator users could access the affected functionality, limiting the exploitability of the v...
CVE-2021-24341
PUBLISHED: 2021-06-14
When deleting a date in the Xllentech English Islamic Calendar WordPress plugin before 2.6.8, the year_number and month_number POST parameters are not sanitised, escaped or validated before being used in a SQL statement, leading to SQL injection.
CVE-2021-24345
PUBLISHED: 2021-06-14
The page lists-management feature of the Sendit WP Newsletter WordPress plugin through 2.5.1, available to Administrator users does not sanitise, validate or escape the id_lista POST parameter before using it in SQL statement, therefore leading to Blind SQL Injection.
CVE-2021-24346
PUBLISHED: 2021-06-14
The Stock in & out WordPress plugin through 1.0.4 has a search functionality, the lowest accessible level to it being contributor. The srch POST parameter is not validated, sanitised or escaped before using it in the echo statement, leading to a reflected XSS issue