{"id":105525,"date":"2022-11-11T21:36:51","date_gmt":"2022-11-11T19:36:51","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/uyazvimost-v-android-pozvolyayushhaya-obojti-blokirovku-ekrana"},"modified":"2022-11-11T21:36:51","modified_gmt":"2022-11-11T19:36:51","slug":"uyazvimost-v-android-pozvolyayushhaya-obojti-blokirovku-ekrana","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/news\/uyazvimost-v-android-pozvolyayushhaya-obojti-blokirovku-ekrana","title":{"rendered":"Ranljivost u Androidu koja omogu\u0107ava zaobila\u017eenje zaklju\u010davanja ekrana.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Na Android platformi otkrivena je ranjivost (CVE-2022-20465) koja omogu\u0107ava onemogu\u0107avanje zaklju\u010davanja ekrana zamjenom SIM kartice i unosom PUK koda. Mogu\u0107nost onemogu\u0107avanja zaklju\u010davanja demonstrirana je na ure\u0111ajima Google Pixel, ali s obzirom na to da popravak utje\u010de na osnovnu kodnu bazu Androida, vjerojatno je da se problem odnosi i na firmware drugih proizvo\u0111a\u010da. Problem je rije\u0161en u studenom skupu ispravki za sigurnost Androida. Istra\u017eiva\u010d koji je uo\u010dio problem primio je nagradu u iznosu od 70 tisu\u0107a dolara od kompanije Google. <\/p>\n

Problem je uzrokovan nepravilnim rukovanjem deblokadom nakon unosa PUK koda (Personal Unblocking Key), koji se koristi za ponovno omogu\u0107avanje rada SIM kartice blokirane nakon vi\u0161ekratnog pogre\u0161nog unosa PIN koda. Da bi se onemogu\u0107ilo zaklju\u010davanje ekrana, dovoljno je u telefon staviti svoju SIM karticu koja je za\u0161ti\u0107ena PIN kodom. Nakon promjene SIM kartice za\u0161ti\u0107ene PIN-om, na ekranu se najprije prikazuje zahtjev za PIN kod. Ako se tri puta pogre\u0161no unese PIN kod, do\u0107i \u0107e do blokade SIM kartice, nakon \u010dega \u0107e biti omogu\u0107eno uno\u0161enje PUK koda za deblokiranje. Ispostavilo se da ispravno uno\u0161enje PUK koda ne samo da deblokira SIM karticu, ve\u0107 i omogu\u0107ava pristup glavnom su\u010delju zaobila\u017eenjem zaklju\u010davanja ekrana, bez potvrde pristupa putem glavne lozinke ili grafi\u010dkog klju\u010da.

\r\n \"Pogledajte\r\n
<\/div>\r\n <\/div><\/center> <\/p>\n

Ranjivost je uzrokovana gre\u0161kom u logici provjere PUK kodova u obradi KeyguardSimPukViewController, koji je zadu\u017een za prikaz dodatnog ekrana za autentifikaciju. U Androidu se koristi nekoliko tipova ekrana za autentifikaciju (za PIN, PUK, lozinku, grafi\u010dki klju\u010d, biometrijsku autentifikaciju) i ti su ekrani pozvani uzastopno kada je potrebno izvr\u0161iti nekoliko provjera, na primjer, kada su potrebni PIN i grafi\u010dki klju\u010d. <\/p>\n

Prilikom ispravnog unosa PIN koda aktivira se druga faza provjere, koja zahtijeva unos glavnog koda za otklju\u010davanje, no prilikom unosa PUK koda sli\u010dna faza se presko\u010di i pristup se odobrava bez zahtjeva za glavnom lozinkom ili grafi\u010dkim klju\u010dem. Preskakanje sljede\u0107e faze otklju\u010davanja doga\u0111a se jer prilikom poziva KeyguardSecurityContainerController#dismiss() ne dolazi do usporedbe o\u010dekivane i izvr\u0161ene metode provjere, tj. obrada smatra da nije do\u0161lo do promjene metode provjere, a zavr\u0161etak provjere PUK koda svjedo\u010di o uspje\u0161nom potvr\u0111ivanju ovlasti. <\/p>\n

Ranljivost je slu\u010dajno otkrivena \u2014 korisniku se ispraznila baterija telefona, a nakon punjenja i uklju\u010divanja, nekoliko puta je pogrije\u0161io pri unosu PIN-a. Nakon toga je otklju\u010dao ure\u0111aj pomo\u0107u PUK koda i bio je iznena\u0111en \u0161to sustav nije zatra\u017eio glavni lozinku koja se koristi za de\u0161ifriranje podataka, nakon \u010dega je ure\u0111aj zapeo s porukom \u201ePixel se pokre\u0107e\u2026\u201d. Korisnik je bio znati\u017eeljan, odlu\u010dio je istra\u017eiti o \u010demu se radi i eksperimentirao je na razne na\u010dine sa unosom PIN- i PUK-kodova, sve dok slu\u010dajno nije zaboravio ponovno pokrenuti ure\u0111aj nakon promjene SIM kartice i umjesto zastoja dobio pristup okru\u017eenju. <\/p>\n

Posebno je zanimljiva reakcija Googlea na izvje\u0161taj o ranjivosti. Informacija o problemu poslana je u lipnju, no do rujna istra\u017eiva\u010d nije mogao dobiti smisleni odgovor. Smatrao je da je takvo pona\u0161anje posljedica \u010dinjenice da nije prvi koji je izvijestio o ovoj gre\u0161ci. Sumnje da ne\u0161to nije u redu pojavile su se u rujnu, kada problem nije bio ispravljen \u010dak ni nakon instalacije a\u017euriranja firmware-a, koje je objavljeno 90 dana kasnije, kada je ve\u0107 istekao navedeni rok za povjerljivost. <\/p>\n

Budu\u0107i da su svi poku\u0161aji da se sazna stanje poslanog izvje\u0161taja o problemu rezultirali samo automatiziranim i \u0161ablonskim odgovorima, istra\u017eiva\u010d je poku\u0161ao osobno kontaktirati radnike Googlea kako bi razjasnio situaciju s pripremom ispravka i \u010dak je demonstrirao ranjivost u londonskom uredu Googlea. Tek nakon toga, rad na uklanjanju ranjivosti je napredovao. U analizi se pokazalo da je o problemu ve\u0107 netko ranije izvijestio, no Google je odlu\u010dio napraviti iznimku i isplatiti nagradu za ponovno izvje\u0161\u0107e o problemu, jer je samo zahvaljuju\u0107i ustrajnosti njegovog autora na problem obratila pa\u017enja.
\n
Izvor: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0412 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0435 Android \u0432\u044b\u044f\u0432\u043b\u0435\u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c (CVE-2022-20465), \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0430\u044f \u043e\u0442\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0443 \u044d\u043a\u0440\u0430\u043d\u0430 \u043f\u0443\u0442\u0451\u043c \u043f\u0435\u0440\u0435\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 SIM-\u043a\u0430\u0440\u0442\u044b \u0438 \u0432\u0432\u043e\u0434\u0430 PUK-\u043a\u043e\u0434\u0430. \u0412\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u043e\u0442\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438 \u043f\u0440\u043e\u0434\u0435\u043c\u043e\u043d\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0430 \u043d\u0430 \u0443\u0441\u0442\u0440\u043e\u0439\u0441\u0442\u0432\u0430\u0445 Google Pixel, \u043d\u043e \u0442\u0430\u043a \u043a\u0430\u043a \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043e\u0441\u043d\u043e\u0432\u043d\u0443\u044e \u043a\u043e\u0434\u043e\u0432\u0443\u044e \u0431\u0430\u0437\u0443 Android, \u0432\u0435\u0440\u043e\u044f\u0442\u043d\u043e, \u0447\u0442\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043a\u0430\u0441\u0430\u0435\u0442\u0441\u044f \u0438 \u043f\u0440\u043e\u0448\u0438\u0432\u043e\u043a \u043e\u0442 \u0434\u0440\u0443\u0433\u0438\u0445 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u0435\u0439. \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0443\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0430 \u0432 \u043d\u043e\u044f\u0431\u0440\u044c\u0441\u043a\u043e\u043c \u043d\u0430\u0431\u043e\u0440\u0435 \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0439 \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0441 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u044c\u044e \u0434\u043b\u044f Android. \u041e\u0431\u0440\u0430\u0442\u0438\u0432\u0448\u0438\u0439 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-105525","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Ranjivost u Androidu koja omogu\u0107uje zaobila\u017eenje zaklju\u010davanja ekrana | ProHoster","description":"U platformi Android otkrivena je ranjivost (CVE-2022-20465) koja omogu\u0107uje isklju\u010divanje zaklju\u010davanja ekrana prebacivanjem SIM kartice i unosom PUK koda.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/news\/uyazvimost-v-android-pozvolyayushhaya-obojti-blokirovku-ekrana","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Android, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0430\u044f \u043e\u0431\u043e\u0439\u0442\u0438 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0443 \u044d\u043a\u0440\u0430\u043d\u0430 | ProHoster","og:description":"\u0412 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0435 Android \u0432\u044b\u044f\u0432\u043b\u0435\u043d\u0430 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c (CVE-2022-20465), \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0430\u044f \u043e\u0442\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0443 \u044d\u043a\u0440\u0430\u043d\u0430 \u043f\u0443\u0442\u0451\u043c \u043f\u0435\u0440\u0435\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 SIM-\u043a\u0430\u0440\u0442\u044b \u0438 \u0432\u0432\u043e\u0434\u0430 PUK-\u043a\u043e\u0434\u0430.","og:url":"https:\/\/prohoster.info\/hr\/blog\/news\/uyazvimost-v-android-pozvolyayushhaya-obojti-blokirovku-ekrana","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2022-11-11T19:36:51+00:00","article:modified_time":"2022-11-11T19:36:51+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":[],"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/105525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=105525"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/105525\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=105525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=105525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=105525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}