It appears another (there have been many the past months) CRITICAL "zero auth" attack for N-Able dropped over the weekend, and N-Able has no response other than "Shut it down and await further instructions" today.

Sorry for linking to poison site, but it's the only place they have a public visible mention of it. Nothing on their site, not even logged in.

https://old.reddit.com/r/Nable/comments/1xrspdf/important_ncentral_critical_security_incident/

I know we're in the age of AI ruining absolutely everything, but the last few months of them calling us ON THE PHONE to insist we patch RIGHT NOW, TODAY leading up to WE HAVE NO PATCH, SHUT IT DOWN is my "last straw" with this company.

Will edit this post when/if I hear back. We're what- 6 hours in as a paying customer and they're full radio silence outside of the email telling us to shut 'er down.

edited again: 8 hours later, absolute radio silence. If you have NABL stock, (not a financial advisor) I suggest you dump it first thing in the morning.

all 21 comments

sorted by: hot top controversial new old
[–] 20 points 10 hours ago (3 children)

Here are the published vulnerabilities, published 15 hours ago: https://github.com/Oracle-Security/CVEs/tree/main/0-Days/N-Central%20N-Able

N-Able status page is saying it's "public disclosure and non-responsible communication of critical vulnerabilities" but according to the GitHub repo author

These are disclosed responsibly and vendors have been contacted. In any instance where it works against the live version, the vendor has not responded to my emails.

It's pretty much he said, she said, but the repo author has no reason to lie about this while the corporate has plenty of reasons...

  • source
  • hideshow 3 child comments
  • [–] 2 points 4 hours ago (1 child)

    "I disclosed 2 unrelated RCEs for a different N-able product, along with a priv esc vulnerability 5 or 6 months ago. These have yet to be patched. I did not disclose any of the 0-days I posted last night," Bales told BleepingComputer.

    https://www.bleepingcomputer.com/news/security/n-able-takes-cloud-platform-offline-after-30-plus-zero-days-published/

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 11 hours ago (8 children)

    Never heard of them before, are (were) they a credible vendor? Their website just seems to have CxO marketing drivel as far as I could be bother navigating.

  • source
  • hideshow 8 child comments
  • [–] 8 points 10 hours ago (6 children)

    Yes. They've been around for years and were owned by Solarwinds for a while. Product is a bit janky but broadly works, about par for the course for enterprise software.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 10 hours ago (1 child)

    Amazing. "Shut it down" is an apocalyptic level response.

    I mean, I've experienced that response on individually compromised hosts/appliances, but not for an entire software suite before.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 9 points 10 hours ago* (last edited 8 hours ago)

    It's their cloud hosted AND self hosted. The entire NCentral platform on AND off-cloud is currently completely shut down. No update from them for 4 hours since the announcement.

    This comes after 2 months of EMERGENCY, DROP WHAT YOU ARE DOING AND PATCH IMMEDIATELY updates- over and over and over.

    edited: words are hard
    edited again: 8 hours later, absolute radio silence. If you have NABL stock, (not a financial advisor) I suggest you dump it first thing in the morning.

  • source
  • parent
  • [–] [S] 4 points 10 hours ago (3 children)

    They're still under that ownership, the company tried to wipe the name off the internet after their last horrific exploit.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 12 points 11 hours ago (6 children)

    Looks like old.reddit is now requiring authentication for me. That’s new.

  • source
  • hideshow 6 child comments
  • [–] 2 points 1 hour ago

    Here's a link to the public incident page. It looks like they are on track to release a fix by mid day tomorrow.

    https://uptime.n-able.com/event/202561/

  • source