back to article Mozilla addons site targeted in same attack that hit Google

The secure webpage hosting addons for Mozilla Firefox was targeted in the same attack that minted a fraudulent authentication credential for Google websites, the maker of the open-source browser said. "DigiNotar informed us that they issued fraudulent certs for addons.mozilla.org in July, and revoked them within a few days of …

COMMENTS

This topic is closed for new posts.
  1. Anonymous Coward
    Anonymous Coward

    Response from Diginotar

    I emailed them asking if they had much to say, their response was

    "At this moment the large browsers removed the DigiNotar root from their trusted list. This is a temporary measure.

    Please read our press release for further details and steps to be taken solve this for our customers."

    Somehow I don't think Mozilla.Chrome will be letting them back in for some time. I wonder if their clients will get refunds on their certificates since they don't work with a big chunk of the clients now.

  2. Crazy Operations Guy
    FAIL

    Gmail, again?

    So it looks like gmail was hacked / intercepted / spied on again; it seems to me that if you have something to hide, don't bother with gmail since just this year t has been China, Iran, and who knows who else.

    1. Tomato42
      Big Brother

      Re: Gmail, again?

      The typical consequences of keeping all you eggs in a single basket.

    2. dave 46

      A reply needs a title?

      I imagine governments want to read the hotmail / yahoo emails of people they are interested in too, I also doubt that these other services are impossible to intercept (especially given the nature of this attack).

      It seems more likely that the other services either don't wish to disclose attacks or just willingly give up information when asked.

  3. Anonymous Coward
    Black Helicopters

    How far beyond DigiNotar does the problem go? Is it systemic?

    So one certificate authority was hacked and didn't say anything to anyone about it until a month later the hack was discovered by an outsider.

    The bogus *.google.com SSL certificate was only discovered because someone was using google chrome a google chrome was recently updated to check for such hacks.

    What if an attacker was going after bank SSL certificates, or Canadian government SSL certificates, not web browser manufacturer SSLs? Who would detect that? And how many months or years would it take before it was stumbled upon?

    And who (other than blackhat hackers) is checking that SSL certificate issuers practice secure measures and have secure systems?

    How many governments around the world have been making bogus SSL certificates as a normal bureaucratic process? Western governments and China to conduct espionage, third world governments and China to steal intellectual property and commit other types of fraud.

  4. Anonymous Coward
    FAIL

    Double Standards?

    "In the absence of a full account of mis-issued certificates from DigiNotar, the Mozilla team moved quickly to remove DigiNotar ......"

    "Nightingale didn't say how many Mozilla certificates were issued and if they were actively used to intercept the communications of people accessing the address"...

    So are all other browser makers now allowed to block access to Mozilla?

  5. Version 1.0 Silver badge
    Devil

    Security, yea - we've heard about it...

    Have you ever looked at the list of "trusted" agencies in your browser? The world and its dog can issue certificates.

    Given that almost anyone can issue certificates and that it's probably foolish to assume that *none* of the Certificate Authorities are compromised at a deep level by one or more foreign governments, let along a bunch of hackers pushing on the backdoor, I think it's safe to say the browser security based on Certificate Authorities is now completely broken.

  6. Anonymous Coward
    WTF?

    well, how would he know?

    "and if they were actively used to intercept the communications of people accessing the address"

    So if $black_hat had the mis-issued cert, and could also poison DNS to point users to the wrong server, that communication would go nowhere near Mozilla.

    To use a car analogy, if someone clones my number plates, I won't be able to tell you if the cloner (or his customer) has committed any other crimes. Until the summons turns up.

  7. Anonymous Coward
    WTF?

    How much we can trust a trusted authority ?

    How much we can trust a trusted authority ? ?

    I thought trusted certificate authority goes through a extensive background checks

    before assigning a wild card certificate..

  8. Bumpy Cat

    Cui bono?

    So is Iran behind this? The targets - Yahoo, Tor, Wordpress, Google (in Iran!) and Baladin (Iranian blogging service) - are pretty strong indicators. None of those are financially lucrative targets in themselves, or much good for spammers who aren't targeting Iranians.

    Having read about some of the stuff the Iranian government got up to in the last three decades, they seem to be rather a law unto themselves. It's rather worrying that they're now targeting online infrastructure.

    1. multipharious

      @Bumpy Cat

      Would seem like that might be the case. They would have access to DNS...

  9. multipharious

    Control of Networks

    I know it is kind of a statement of the obvious, but the bogus Certificates are still only of value for the attackers if there is a possibility to redirect. In other words, they have to either control the network at a macro scale or control where the users are directed from some local method of fraudulent name resolution. DNS control or malware for redirection. Either are required. This exploit is no good alone.

    That said, I wonder how many account/password combos got skimmed. No warnings about that? Hmph.

    @AC 09:56 GMT, I am with you on this! They would have no idea. Fake login screen...grab the credentials...

  10. Anonymous Coward
    Anonymous Coward

    Tor says you didn't contact them.

    http://identi.ca/notice/82241336

    Perhaps you tried the wrong email address, or maybe it fell into a spam filter en route?

This topic is closed for new posts.

Other stories you might like