Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Fistful of flaws blow away SolarWinds network appliances

Five nasties await netadmins

Admins of SolarWinds system management systems can block out a biggish chunk of their diaries to implement a bunch of serious patches.

There are five bugs of varying seriousness in the company's Log and Event Manager appliance discovered by KoreLogic and posted to Full Disclosure.

Four of the bugs depend on an attacker accessing the appliance's SSH shell and logging in as cmc, if the admin has left that user's default password – password – in place.

First, there's a sudo path that's a privilege escalation vector: an attacker only needs a bit of directory traversal to execute commands as root.

There's also a script (upgrade21.sh) that lets the attacker change permissions for any file, thereby rooting the system.

An input validation bug lets the same SSH user escape the shell and execute arbitrary commands. There's also a less-serious file-read bug.

For good measure, the remaining bug doesn't depend on the defaults above. A Postgres database ships with default credentials, and while SolarWinds blocked it being attacked over IPv4, they missed the fix in IPv6.

SolarWinds has shipped a hotfix here. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like