Live data from Hacker News

One-Click RCE in Asus's Preinstalled Driver Software

mrbruh.com

231–240 of 253 posts

Re: One-Click RCE in Asus's Preinstalled Driver Software

#231

Earlier quoted context omitted.

I think ASUS' turnaround time on this was quite good, I don't see the problem here. ASUS didn't deny the bug, didn't threaten to prosecute anyone for reverse engineering their software, and quickly patched their software. I have no doubt that before the days of responsible disclosure, this process would've taken months and might have involved the police. Normal people don't care about vulnerabilities. They use phones…

>They say “This issue is limited to motherboards and does not affect laptops, desktop computers”, however this affects any computer including desktops/laptops that have DriverHub installed >instead of them saying it allows for arbitrary/remote code execution they say it “may allow untrusted sources to affect system behaviour”. Sounds like Asus did in fact deny the bug.

I call this "save the face" move. I once reported suspected card skimming at an ATM. The skimmer was integrated, so it would be an inside job. The bank said ATMs can malfunction sometimes, but both ATMs are replaced with different ones in a couple of days.

Re: One-Click RCE in Asus's Preinstalled Driver Software

#233
post #165

Earlier quoted context omitted.

I think ASUS' turnaround time on this was quite good, I don't see the problem here. ASUS didn't deny the bug, didn't threaten to prosecute anyone for reverse engineering their software, and quickly patched their software. I have no doubt that before the days of responsible disclosure, this process would've taken months and might have involved the police. Normal people don't care about vulnerabilities. They use phones…

> Stores are not permitted to sell products with known vulnerabilities under new cybersecurity regulations. What are the specifics on that? Like does the vulnerability need to be public or is it enough if just the vendor knows about it? Does everyone need to stop selling it right away if new vulnerability is discovered or do they some time patch it? I'm pretty sure software like Windows almost definitely has some unf…

The full legal text doesn't fit in a HN comment, but I believe this is the meat of the description: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:...

Note that in the legal text above there is language stating what requirements from the annexes applies to what hard/software.

As far as I know (I haven't read the text fully) selling stuff is fine if the end user can update their software.

There is no clear description of what "vulnerability" entails. The definitions do include things like:

    ‘vulnerability’ means a weakness, susceptibility or flaw of a product with digital elements that can be exploited by a cyber threat;
    ‘cyber threat’ means a cyber threat as defined in Article 2, point (8), of Regulation (EU) 2019/881;
    ‘cybersecurity risk’ means the potential for loss or disruption caused by an incident and is to be expressed as a combination of the magnitude of such loss or disruption and the likelihood of occurrence of the incident;

Re: One-Click RCE in Asus's Preinstalled Driver Software

#234

Earlier quoted context omitted.

I think ASUS' turnaround time on this was quite good, I don't see the problem here. ASUS didn't deny the bug, didn't threaten to prosecute anyone for reverse engineering their software, and quickly patched their software. I have no doubt that before the days of responsible disclosure, this process would've taken months and might have involved the police. Normal people don't care about vulnerabilities. They use phones…

"Stores are not permitted to sell products with known vulnerabilities under new cybersecurity regulations." Do stores have to patch known vulnerabilities before releasing the product to customers or can customers install the patch?

I believe it's okay to let customers install the patch. The regulation itself can be found here: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML

Basically, the manufacturer has to issue a patch, and the distributor has to ensure that the patch is available before selling the vulnerable devices. Without secure software, the product is essentially CE-incompliant, which means it practically isn't allowed to be sold.

IANAL though.

Re: One-Click RCE in Asus's Preinstalled Driver Software

#235
post #219

Earlier quoted context omitted.

Spectre/Meltdown is the perfect example of a vendor, Intel and AMD, deflecting blame onto the OS and software producers, successfully avoiding a recall, avoiding refunds for decreased performance and avoiding most of the blame. What actually should have happened there is a full recall of all affected hardware. Microcode fixes and payments for lost performance in the mean time, until the new hardware arrives. Meltdown…

There is no world in which a recall (and/or a refund) is ever possible. Until it is demonstrated that such flaws are a life and death fault, no regulation is possible for such flaws (unlike cars - which do have such recalls for faults that have life and death implications).

In the world of physical goods, that is totally normal. Only software is different. And maybe the US.

Re: One-Click RCE in Asus's Preinstalled Driver Software

#236
post #204

Earlier quoted context omitted.

"Licensed professional engineers" are a software-development myth. If all our software was as simple as a bridge, then we could have that. A bridge is 5 sheets of plans, 10 pages of founding checks, 30 pages of calculations, 100 pages of material specs. You can read all those in a day. Check the calculations in a week. Next bridge will be almost the same. Now tell me about any software where the spec is that short an…

> We always build something new and bespoke, with extremely high complexity compared to any kind of building or infrastructure. Maybe this is part of the problem?

The world of software development is just different. Copying software is a solved problem, it is easy, cheap and totally normal. Whenever you start your software it is going to be copied around a few times. So the trivial "same bridge as last time, just over the next river" doesn't really exist in software. The software world has that situation solved, you get your software plus the (if so inclined) recommended OS and hardware to run it on, install it and you are fine. You can do it 1000 times over and verify that things are the same. You can even do it automatically. You can do it 1000 times over on different hardware, just rerun the test suite if you are paranoid, done. This is the level of triviality that is solved by licensed engineers when doing bridges.

Now in a few years, when maybe 3D-printing for buildings takes off, all that "fun" that is now bespoke software development will also arrive in architecture. THEN things will really be ugly ;)

Re: One-Click RCE in Asus's Preinstalled Driver Software

#237

Responsible Disclosures and their consequences have been a disaster for the human race. Companies need to feel a lot more pain a lot more often in order for them to take the security of their customers a lot more serious. If you just give them month to fix an issue and spoon-feed them the solution it's just another ticket in their Backlog. But if every other security issue becomes enough news online that their CEOs a…

I think ASUS' turnaround time on this was quite good, I don't see the problem here. ASUS didn't deny the bug, didn't threaten to prosecute anyone for reverse engineering their software, and quickly patched their software. I have no doubt that before the days of responsible disclosure, this process would've taken months and might have involved the police. Normal people don't care about vulnerabilities. They use phones…

It's still hilarious how the police will get involved for you tinkering with your own computer inside your own home.

Re: One-Click RCE in Asus's Preinstalled Driver Software

#238
>DriverHub only responded to requests with the origin header set to “driverhub.asus.com”. So at least this software wasn’t completely busted and evil hackers can’t just send requests to DriverHub willy-nilly.

>When I switched the origin to driverhub.asus.com.mrbruh.com, it allowed my request.

One more CVE to developers validating URLs in some silly way

Your language comes with a URL parser. Use it! You can't handle all the edge cases of the URL format by yourself.

    if ((new URL("https://user:password@driverhub.asus.com/whatever?q=whatever#whatever")).hostname === "driverhub.asus.com") { ... }

Re: One-Click RCE in Asus's Preinstalled Driver Software

#239

Earlier quoted context omitted.

"Stores are not permitted to sell products with known vulnerabilities under new cybersecurity regulations." Do stores have to patch known vulnerabilities before releasing the product to customers or can customers install the patch?

I believe it's okay to let customers install the patch. The regulation itself can be found here: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML Basically, the manufacturer has to issue a patch, and the distributor has to ensure that the patch is available before selling the vulnerable devices. Without secure software, the product is essentially CE-incompliant, which means it practically isn't allowed to be sold.…

This sounds like another bureaucratic nightmare. Who is going to track this?

Re: One-Click RCE in Asus's Preinstalled Driver Software

#240
> This is understandable since ASUS is just a small startup and likely does not have the capital to pay a bounty.

ASUS is not a small startup. It simply and only minds the money they suck FROM customers. There is no other way around to push money TO customers.

But the real point is: how much would be worth selling such an exploit to a malicious agent? Likely more than USD 0.00.

But then again, ASUS doesn't mind about that. Sad truth.

Post reply on HN