{"id":32527,"date":"2019-10-31T21:47:32","date_gmt":"2019-10-31T18:47:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/dockerhub-vzloman\/"},"modified":"2019-10-31T21:47:32","modified_gmt":"2019-10-31T18:47:32","slug":"dockerhub-vzloman","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/dockerhub-vzloman","title":{"rendered":"DockerHub bol napadnut\u00fd.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"DockerHub
\n
\nPred p\u00e1r hodinami boli niektor\u00fdm pou\u017e\u00edvate\u013eom DockerHub zaslan\u00e9 e-maily s nasleduj\u00facim obsahom:<\/p>\n

\u201eVo \u0161tvrtok 25. apr\u00edla 2019 sme zistili neopr\u00e1vnen\u00fd pr\u00edstup k jednej z datab\u00e1z DockerHub, ktor\u00e1 obsahuje \u010das\u0165 nefinan\u010dn\u00fdch \u00fadajov pou\u017e\u00edvate\u013eov. Po zisten\u00ed sme okam\u017eite urobili v\u0161etko potrebn\u00e9 na ochranu \u00fadajov pou\u017e\u00edvate\u013eov. <\/p>\n

A teraz by sme sa radi podelili o inform\u00e1cie, ktor\u00e9 sme dok\u00e1zali z\u00edska\u0165 po\u010das vy\u0161etrovania, vr\u00e1tane toho, ktor\u00e9 \u00fa\u010dty DockerHub boli zasiahnut\u00e9 a ak\u00e9 kroky by mali ich vlastn\u00edci teraz podnikn\u00fa\u0165.
\n<\/a><\/noindex>
\nToto s\u00fa na\u0161e zistenia: <\/p>\n

Po\u010das kr\u00e1tkeho obdobia neopr\u00e1vnen\u00e9ho pr\u00edstupu k datab\u00e1ze DockerHub mohli by\u0165 odhalen\u00e9 d\u00f4vern\u00e9 \u00fadaje pribli\u017ene 190 000 \u00fa\u010dtov (menej ako 5 % pou\u017e\u00edvate\u013eov slu\u017eby). \u00dadaje zah\u0155\u0148aj\u00fa men\u00e1 pou\u017e\u00edvate\u013eov a hashe hesiel mal\u00e9ho percenta z uveden\u00fdch pou\u017e\u00edvate\u013eov, ako aj tokeny GitHub a BitBucket, ktor\u00e9 sa pou\u017e\u00edvaj\u00fa na automatick\u00e9 zostavenie kontajnerov. <\/p>\n

\u010co by sa malo teraz urobi\u0165: <\/p>\n

\u2014 \u017diadame pou\u017e\u00edvate\u013eov, aby si zmenili hesl\u00e1 DockerHub a ak\u00fdchko\u013evek in\u00fdch \u00fa\u010dtov, ktor\u00e9 pou\u017e\u00edvaj\u00fa rovnak\u00e9 heslo. <\/p>\n

\u2014 Pou\u017e\u00edvate\u013eom, ktor\u00ed vyu\u017e\u00edvali automatick\u00e9 zostavenia a ktor\u00fdch sa to mohlo dotkn\u00fa\u0165, sme resetovali tokeny a pr\u00edstupov\u00e9 k\u013e\u00fa\u010de. \u017diadame ich, aby si tie\u017e overili svoje repozit\u00e1re na pr\u00edtomnos\u0165 ned\u00e1vnej podozrivej aktivity. <\/p>\n

\u2014 Ak chcete zisti\u0165, ako presk\u00fama\u0165 podozriv\u00fa aktivitu vo svojich \u00fa\u010dtoch GitHub a BitBucket za posledn\u00fdch 24 hod\u00edn, prejdite na nasleduj\u00face odkazy: help.github.com\/en\/articles\/reviewing-your-security-log<\/a><\/noindex> a bitbucket.org\/blog\/new-audit-logs-give-you-the-who-what-when-and-where<\/a><\/noindex> <\/p>\n

\u2014 M\u00f4\u017ee to ovplyvni\u0165 va\u0161e aktu\u00e1lne zostavy z na\u0161ich slu\u017eieb automatick\u00fdch zostaven\u00ed. Rovnako m\u00f4\u017ee by\u0165 potrebn\u00e9 odpoji\u0165 a znova pripoji\u0165 va\u0161e \u00fa\u010dty GitHub a BitBucket. O tom je podrobne p\u00edsan\u00e9 tu: docs.docker.com\/docker-hub\/builds\/link-source<\/a><\/noindex> <\/p>\n

My sa posna\u017e\u00edme o zlep\u0161enie na\u0161ich bezpe\u010dnostn\u00fdch syst\u00e9mov a prehodnot\u00edme na\u0161e politiky. Navy\u0161e sme nastavili \u010fal\u0161ie metriky na sledovanie mo\u017enej neleg\u00e1lnej aktivity v bud\u00facnosti. <\/p>\n

St\u00e1le vy\u0161etrujeme incident a budeme v\u00e1s informova\u0165, ak sa objavia nov\u00e9 detaily.\u201d<\/p>\n

Ako zvy\u010dajne, kontrolujeme vlastn\u00fa po\u0161tu, svoje \u00fa\u010dty v uveden\u00fdch slu\u017eb\u00e1ch, znova si vym\u00fd\u0161\u013eame hesl\u00e1. Ak sa objavia nov\u00e9 inform\u00e1cie, tento pr\u00edspevok aktualizujeme.<\/p>\n

Len registrovan\u00ed pou\u017e\u00edvatelia sa m\u00f4\u017eu z\u00fa\u010dastni\u0165 prieskumu. Prihl\u00e1ste sa<\/a><\/noindex>, pros\u00edm.<\/p>\n

Dostali ste podobn\u00fd e-mail?<\/h2>\n