all 5 comments

sorted by: hot top controversial new old
[–] 30 points 4 months ago (1 child)

This is how you create people like Nightmare Eclipse.

These people are going out of their way to responsibly disclose vulnerabilites to the bug bounty programs and being treated poorly as a result. Granted, AMD technically didn't have to pay since it was a MITM attack, but they could have at least handled the whole interaction better.

  • source
  • hideshow 1 child comment
  • [–] 8 points 4 months ago*

    And simply paid they guy out of appreciation.

    I generally support the model we've had for bBug disclosure - it's about preventing zero days - which protects the users of these products.

    But for AMD stuff now, go ahead and sell your discoveries, let the zero-days ruin AMDs marketing.

  • source
  • parent
  • [–] 21 points 4 months ago (1 child)

    $10k is nothing to AMD. The middle-management bean counters making these decisions are actively harming their company's (and user's security.

  • source
  • hideshow 1 child comment
  • [–] 4 points 4 months ago

    The flaw of not using HTTPS for the downloads is so basic it's shocking they didn't have internal tooling to raise this before it was shipped. I'm not familiar with AMD's bug bounty policy but they should have at least paid $1337 to the researcher for raising this to them.

  • source
  • parent
  • [–] 13 points 4 months ago

    Nightmare Eclipse 2.0 incoming. 10K for such a thing is absolutely nothing for companies like AMD. Why promise rewards if at the end, you don't intend to pay? This has been a growing trend in the bug bounty space. Many times a bug is marked as duplicate and is fixed secretly. Other times, they're straightaway rejected..

  • source
  • 46 comments in c/technology@lemmy.world view that post
    [–] 181 points 4 months ago (10 children)

    Didn't Microsoft just pull this same thing and now there's all these 0-days getting released publicly as vengeance? I swear, all these companies are sharing the same brain cell...

  • source
  • hideshow 10 child comments
  • [–] 96 points 4 months ago (6 children)

    all these companies are sharing the same brain cell…

    they all have upper management that went to the same schools and the same classes, so they're all indoctrinated the same way.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 42 points 4 months ago

    And the people in the houses
    All went to the university
    Where they were put in boxes
    And they came out all the same

    And there's doctors and lawyers
    And business executives
    And they're all made out of ticky-tacky
    And they all look just the same

    And they all play on the golf course
    And drink their martinis dry
    And they all have pretty children
    And the children go to school

    And the children go to summer camp
    And then to the university
    Where they are put in boxes
    And they come out all the same

    https://youtu.be/XUwUp-D_VV0

  • source
  • parent
  • [–] 18 points 4 months ago (3 children)

    Plus they are following the lead of the leadership of the country, which is cheating everyone that you are able to.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 12 points 4 months ago (2 children)

    Trump too has a degree in economics and went to a prestigious finance school so that tracks.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 166 points 4 months ago (1 child)

    Nothing quite like creating a specific incentive for researchers to seek "alternative" sources of income as payment for their research efforts.

    Microsoft tried this .. seems to be working out for them .. not.

  • source
  • hideshow 1 child comment
  • [–] 125 points 4 months ago

    Well the next time someone finds a bug in their software they will have to find other ways to monetize it.

  • source
  • [–] 120 points 4 months ago

    My favourite part was when they rejected the flaw saying it's out of scope for their bounty program but still wanted him to keep it secret because of the rules of the bounty program. The same bounty program that didn't cover it.

  • source
  • [–] 92 points 4 months ago*

    They really do be stepping over dollars to pick up pennies.

    Or in this case, to save them.

  • source
  • [–] 70 points 4 months ago (10 children)

    AMD told MrBruh that all update communications now use HTTPS and that updates undergo signature verification. The researcher says he verified the HTTPS claim, but found only a CRC32 check on the downloaded executable, which is not considered a cryptographic signature.

    This is the most shocking part. You’d think that AMD as a high-tech company has some smart people working for them. These are very basic things that any half decent programmers should get right. If at no part of the process of implementing this anyone brought up that this is not secure, that is extremely worrying and indicative of a very broken development process. It’s not like a proper cryptographic signature costs extra. This is just pure incompetence.

  • source
  • hideshow 10 child comments
  • [–] 24 points 4 months ago (6 children)

    The problem with using CRC32 is it reversible and has high collusion rate. An attacker can easily make a file the generates the same hash. This tool a few minutes of searching online. It appears that people who work at AMD don't even know how to do proper research. All they have to do is look up how to make a secure updating process.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 15 points 4 months ago

    The problem is that a CRC32 checksum is not a signature. Doesn't matter if they use the most complex checksum in the world or not, what they need here is a signature

  • source
  • parent
  • [–] 3 points 4 months ago (3 children)

    What does it matter if it's CRC or sha512 if they are using an unsecured connection to transmit them? A stranger who has already acquired capability to modify the payload in transit can also modify the checksum. A better hash will not solve this problem.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 4 months ago* (2 children)

    They use https now, but use CRC for signature verification:

    AMD told MrBruh that all update communications now use HTTPS and that updates undergo signature verification. The researcher says he verified the HTTPS claim, but found only a CRC32 check on the downloaded executable, which is not considered a cryptographic signature.

    I could be wrong here, but I believe they should use a combination of SHA256 and PGP for signature verification.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 months ago* (1 child)

    Oh, okay, so maybe I misread the sentence. I thought the implication was they used crc32 as opposed to HTTPS. Not sure why you need an additional layer in addition to https- as long as the certificate chain is setup properly. And again, you're not gaining additional security if you submit the hash (or a gpg key) through the same channel. So if they already use https and just want to check for broken downloads, crc32 is perfectly fine. It's just security theater at that point.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 4 months ago

    An attacker can still send a compromised payload if there's no signature verification of the update. It takes a more sophisticated attack (e.g. supply chain attack, hijacking AMD's update website, etc.) but it has happened before to other companies. If the payload is signed and verified, an attacker would also need to gain access to AMD's private key to successfully send out a bad update. Assuming reasonable security, getting that private key would be a lot harder to get on top of somehow compromising AMD's update web service.

    Also CRC checks over the internet are sort of silly and redundant since every packet sent would already be subject to a similar CRC check and bad packets would be ignored (dropped and re-requested). It would only prevent corruption on disk or in memory which are a lot less likely than transmission corruption.

  • source
  • parent
  • [–] 15 points 4 months ago

    Not surprising at all. I work in IT and security is by and large reactionary and based on scans that are often rudimentary. As far as training devs on good security practices there's next to nothing. You learn from getting your hand slapped or you don't learn at all.

  • source
  • parent
  • load more comments (1 reply)
    [–] 60 points 4 months ago

    Advertising that you stiff smart people who know your architecture? Good luck AMD.

  • source
  • [–] 47 points 4 months ago (1 child)

    This is going to work out really well for AMD. Any future vulnerabilities will most certainly be reported to them, responsibly. Right?

  • source
  • hideshow 1 child comment
  • [–] 42 points 4 months ago

    Have they not understood what currently is happening with Microsoft?

  • source
  • [–] 68 points 4 months ago (3 children)

    A long time ago I felt like bug bounty programs would be an amazing way forward... Now I'm firmly in the camp of fuck it, sell it to the highest bidder.

  • source
  • hideshow 3 child comments
  • [–] 24 points 4 months ago

    I swear, AMD and Microsoft are two brain cells competing for third place

  • source
  • [–] 10 points 4 months ago (1 child)

    Again that means they don't want anyone to report or fix security plot flaws.

  • source
  • hideshow 1 child comment
  • [–] 1 point 4 months ago (1 child)

    I don't have all the facts but based on the article I don't see the problem everyone seems upset about.

    They received the report, decided it was valid but didn't match a bounty. Then asked him to follow standard responsible disclosure processes giving him credit in the final release. All very standard.

    Should there have been a bounty? AMD has the budget, probably yes. But nothing in the communications seems any different from what I've seen and have received similar from companies in the past.

  • source
  • hideshow 1 child comment
  • [–] 18 points 4 months ago

    Except when he responsibly disclosed to AMD, they closed the ticket as "out of scope" without any further communication. He then made a blog post about it warning other users about the vulnerability since ostensibly, AMD didn't want to fix it. Only after that post had gone viral AMD suddenly came back saying that despite the ticket being closed as such, their internal security team was still analysing it and he should've somehow known that and that he violated the TOC of the bug bounty program (remember, after saying that the vulnerability was out of scope of the program). Additionally AMD then changes those terms a month after the initial ticket to suddenly say that even if the ticket is refused, you're still not allowed to talk about it. Then to top it off they take a month longer to fix it then is industry standard, don't disclose the fix to the researcher as is customary until a few days before release and only because he kept badgering them and as the cherry don't tell their users that the only way to securely fix this is by uninstalling and reinstalling. Everything about it is scummy behaviour all around.

  • source
  • parent
  • [+] -14 points 4 months ago (5 children)

    Fuuuuuck. I guess I'm switching back to Intel. I really don't want to give money to NVidia, þough.

  • source
  • hideshow 5 child comments
  • [–] 17 points 4 months ago (1 child)

    Nvidia has a large, multibillion dollar stake in Intel. Additionally, the federal government has a 10% stake in Intel.

  • source
  • parent
  • hideshow 1 child comment
  • [–] -1 points 4 months ago

    Oh, yeah. I forgot about Trump's graft project. Well, hopefully it won't be too long before a RISCV CPU becomes a viable alternative, but I'm not too optimistic. My experience wiþ ARM64 is þat a lot of software still isn't available and doesn't compile for it, and RISCV is so far behind. Even if it catches up to ARM in speed (much less AMD64), it's going to be forever before þe cornucopia of FOSS catches up.

  • source
  • parent
  • [–] 3 points 4 months ago

    All tech companies suck at some level. I choose AMD cause I've had good experiences with their products. Not for any moral reasons. There is no moral consumerism when it comes to silicone. So just choose what you like and try not to think too hard about it.

  • source
  • parent