{"id":10955,"date":"2022-08-29T12:19:15","date_gmt":"2022-08-29T09:19:15","guid":{"rendered":"https:\/\/www.kaspersky.com.tr\/blog\/?p=10955"},"modified":"2022-08-29T12:19:15","modified_gmt":"2022-08-29T09:19:15","slug":"signal-hacked-but-still-secure","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.tr\/blog\/signal-hacked-but-still-secure\/10955\/","title":{"rendered":"Hackerlar sayesinde Signal&#8217;in g\u00fcvenli oldu\u011fu kan\u0131tland\u0131"},"content":{"rendered":"<p>Signal ekibi 14 A\u011fustos\u2019ta bilinmeyen baz\u0131 hackerlar\u0131n mesajla\u015fma uygulamas\u0131 kullan\u0131c\u0131lar\u0131na sald\u0131rd\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/support.signal.org\/hc\/en-us\/articles\/4850133017242\" target=\"_blank\" rel=\"noopener nofollow\">bildirdi<\/a>. Bu olay\u0131n neden Signal\u2019in di\u011fer baz\u0131 mesajla\u015fma uygulamalar\u0131na g\u00f6re daha avantajl\u0131 olmas\u0131n\u0131n bir g\u00f6stergesi oldu\u011funu a\u00e7\u0131kl\u0131yoruz.<\/p>\n<h2>Ne oldu?<\/h2>\n<p>Signal\u2019in yay\u0131nlad\u0131\u011f\u0131 a\u00e7\u0131klamaya g\u00f6re sald\u0131r\u0131, uygulaman\u0131n yakla\u015f\u0131k 1900 kullan\u0131c\u0131s\u0131n\u0131 etkiledi. Signal\u2019in kitlesinin ayda 40 milyon aktif kullan\u0131c\u0131dan <a href=\"https:\/\/www.feedough.com\/signal-statistics-usage-revenue-key-facts\/\" target=\"_blank\" rel=\"noopener nofollow\">fazla<\/a> oldu\u011funu d\u00fc\u015f\u00fcnd\u00fc\u011f\u00fcm\u00fczde olay\u0131n \u00e7ok k\u00fc\u00e7\u00fck bir kesimi etkiledi\u011fi g\u00f6r\u00fcl\u00fcyor. Bununla birlikte, Signal a\u011f\u0131rl\u0131kl\u0131 olarak yaz\u0131\u015fmalar\u0131n\u0131n gizlili\u011fine ger\u00e7ekten \u00f6nem veren ki\u015filer taraf\u0131ndan kullan\u0131l\u0131yor. Bu y\u00fczden sald\u0131r\u0131 kullan\u0131c\u0131lar\u0131n \u00e7ok k\u00fc\u00e7\u00fck bir k\u0131sm\u0131n\u0131 etkilemi\u015f olsa da g\u00fcvenlik d\u00fcnyas\u0131nda yank\u0131 buldu.<\/p>\n<p>Sald\u0131r\u0131 sonucunda hackerlar kurbanlar\u0131n hesaplar\u0131na ba\u015fka bir cihazdan giri\u015f yapabilmeyi ya da belirli bir telefon numaras\u0131n\u0131n Signal kulland\u0131\u011f\u0131n\u0131 belirleyebilmeyi ba\u015fard\u0131. Hackerlar bu 1900 ki\u015fi aras\u0131ndan spesifik olarak \u00fc\u00e7 ki\u015fiyle ilgileniyordu. Bu \u00fc\u00e7 kullan\u0131c\u0131dan biri, Signal\u2019a hesab\u0131n\u0131n bilgisi d\u0131\u015f\u0131nda ba\u015fka bir cihazda etkinle\u015ftirildi\u011fini bildirdi.<\/p>\n<h2>Nas\u0131l oldu?<\/h2>\n<p>Kaspersky Daily sayfalar\u0131nda s\u0131k s\u0131k Signal\u2019in g\u00fcvenli bir mesajla\u015fma uygulamas\u0131 oldu\u011fu <a href=\"https:\/\/www.kaspersky.com\/blog\/private-data-messengers\/10611\/\" target=\"_blank\" rel=\"noopener nofollow\">hakk\u0131nda<\/a> <a href=\"https:\/\/www.kaspersky.com\/blog\/signal-privacy-security\/40377\/\" target=\"_blank\" rel=\"noopener nofollow\">konu\u015fuyoruz<\/a>, fakat uygulama yine de sald\u0131r\u0131ya u\u011frad\u0131. Peki bu, uygulaman\u0131n me\u015fhur g\u00fcvenlik ve gizlilik y\u00f6n\u00fcn\u00fcn bir mitten ibaret oldu\u011funu mu g\u00f6steriyor? Sald\u0131r\u0131n\u0131n tam olarak nas\u0131l ger\u00e7ekle\u015fti\u011fine ve Signal\u2019in bu sald\u0131r\u0131daki esas rol\u00fcne bir bakal\u0131m.<\/p>\n<p>Signal hesaplar\u0131n\u0131n t\u0131pk\u0131 WhatsApp ve Telegram\u2019da oldu\u011fu gibi bir telefon numaras\u0131na ba\u011fl\u0131 olmas\u0131yla ba\u015flayal\u0131m. \u0130stisnalar g\u00f6r\u00fclse de yayg\u0131n uygulama bu \u015fekilde. \u00d6rne\u011fin, g\u00fcvenli mesajla\u015fma uygulamas\u0131 Threema, hesaplar\u0131 telefon numaras\u0131na ba\u011flamamay\u0131 avantajlar\u0131ndan biri olarak say\u0131yor. Signal\u2019de ise telefon numaras\u0131 <a href=\"https:\/\/www.kaspersky.com.tr\/blog\/identification-authentication-authorization-difference\/8851\/\" target=\"_blank\" rel=\"noopener\">kimlik do\u011frulama<\/a> i\u00e7in gerekli; kullan\u0131c\u0131n\u0131n girdi\u011fi telefon numaras\u0131na g\u00fcvenlik kodunu i\u00e7eren mesaj g\u00f6nderiliyor. Bu kodun uygulamaya girilmesi gerekiyor. Do\u011fru kod girilirse kullan\u0131c\u0131n\u0131n ger\u00e7ekten de bu numaran\u0131n sahibi oldu\u011fu kan\u0131tlanm\u0131\u015f oluyor.<\/p>\n<p>Tek seferlik kodlar i\u00e7eren bu t\u00fcr metin mesajlar\u0131n\u0131n g\u00f6nderimi, birden \u00e7ok servis i\u00e7in ayn\u0131 kimlik do\u011frulama hizmetini sa\u011flayan \u00f6zel \u015firketler tarar\u0131ndan ger\u00e7ekle\u015ftiriliyor. Signal \u00f6rne\u011finde bu sa\u011flay\u0131c\u0131 Twilio adl\u0131 bir \u015firket. Hackerlar da tam olarak bu \u015firketi hedef ald\u0131.<\/p>\n<p>Bir sonraki a\u015fama kimlik av\u0131. Baz\u0131 Twilio \u00e7al\u0131\u015fanlar\u0131, parolalar\u0131n\u0131n s\u00fcresinin doldu\u011funu ve g\u00fcncellemeleri gerekti\u011fini s\u00f6yleyen mesajlar <a href=\"https:\/\/www.twilio.com\/blog\/august-2022-social-engineering-attack\" target=\"_blank\" rel=\"noopener nofollow\">ald\u0131<\/a>. Bunu yapmak i\u00e7in bir ba\u011flant\u0131ya t\u0131klamalar\u0131 isteniyordu ve bu (tahmin etti\u011finiz gibi) bir kimlik av\u0131 ba\u011flant\u0131s\u0131yd\u0131. \u00c7al\u0131\u015fanlardan biri yemi yuttu, sahte siteye giderek kimlik bilgilerini girdi ve bu bilgiler do\u011frudan hackerlar\u0131n eline ge\u00e7mi\u015f oldu.<\/p>\n<p>Twilio\u2019nun dahili sistemine eri\u015fim veren bu kimlik bilgileri, kullan\u0131c\u0131lara mesaj g\u00f6nderebilmelerini ve bu mesajlar\u0131 okuyabilmelerini sa\u011flad\u0131. Ard\u0131ndan hackerlar bu servisi kullanarak yeni bir cihaza Signal kurdu. Kurban\u0131n telefon numaras\u0131n\u0131 girdiler, aktivasyon kodunu i\u00e7eren mesaj\u0131 ele ge\u00e7irdiler ve Signal hesab\u0131na girmi\u015f oldular.<\/p>\n<h2>Bu olay nas\u0131l Signal\u2019in sa\u011flaml\u0131\u011f\u0131n\u0131 kan\u0131tl\u0131yor<\/h2>\n<p>Signal\u2019in bile bu t\u00fcr olaylardan muaf olmad\u0131\u011f\u0131 ortaya \u00e7\u0131kt\u0131. Peki niye s\u00fcrekli Signal\u2019in g\u00fcvenli\u011finden ve gizlili\u011finden bahsedip duruyoruz?<\/p>\n<p>Birincisi, <strong>siber su\u00e7lular yaz\u0131\u015fmalara eri\u015fim sa\u011flayamad\u0131<\/strong>. Signal, g\u00fcvenli <a href=\"https:\/\/signal.org\/docs\/\" target=\"_blank\" rel=\"noopener nofollow\">Signal Protokol\u00fc\u2019ne<\/a> sahip <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/end-to-end-encryption\/\" target=\"_blank\" rel=\"noopener\">u\u00e7tan uca \u015fifreleme<\/a> kullan\u0131yor. U\u00e7tan uca \u015fifreleme kullan\u0131ld\u0131\u011f\u0131 i\u00e7in kullan\u0131c\u0131 mesajlar\u0131 yaln\u0131zca kullan\u0131c\u0131lar\u0131n kendi cihazlar\u0131nda saklan\u0131yor, Signal\u2019in sunucular\u0131nda ya da herhangi ba\u015fka bir yerde depolanm\u0131yor. Bu y\u00fczden yaln\u0131zca Signal\u2019in altyap\u0131s\u0131n\u0131 hackleyerek bu mesajlar\u0131 okuyabilmenin hi\u00e7bir yolu yok.<\/p>\n<p>Signal\u2019in sunucular\u0131nda <em>depolanan<\/em> \u015fey ise, kullan\u0131c\u0131lar\u0131n ve rehberlerinde bulunan ki\u015filerin telefon numaralar\u0131. Uygulama bu sayede rehberinizdeki ki\u015filerden biri Signal\u2019e kat\u0131ld\u0131\u011f\u0131nda size bildirim g\u00f6nderebiliyor. Ancak bu veriler, birincisi, Signal geli\u015ftiricilerinin bile eri\u015femedi\u011fi g\u00fcvenli alan ad\u0131 verilen g\u00fcvenli depolarda saklan\u0131yor. \u0130kincisi, numaralar d\u00fcz metin olarak de\u011fil, bir t\u00fcr hash kodu \u015feklinde depolan\u0131yor. Bu mekanizma, telefonunuzdaki Signal uygulamas\u0131n\u0131n rehberinizdeki ki\u015filer hakk\u0131nda \u015fifrelenmi\u015f bilgi g\u00f6nderebilmesini ve i\u00e7lerinden hangilerinin Signal kulland\u0131\u011f\u0131na dair ayn\u0131 \u015fekilde \u015fifrelenmi\u015f yan\u0131tlar alabilmesini sa\u011fl\u0131yor. Di\u011fer bir deyi\u015fle, <strong>sald\u0131rganlar kullan\u0131c\u0131lar\u0131n rehberlerine de eri\u015fim sa\u011flayamad\u0131<\/strong>.<\/p>\n<p>Son olarak, Signal\u2019in tedarik zincirinden, \u015firketin kulland\u0131\u011f\u0131 daha az korunan bir servis sa\u011flay\u0131c\u0131 \u00fczerinden sald\u0131r\u0131ya u\u011frad\u0131\u011f\u0131n\u0131 vurgulamak gerekiyor. Dolay\u0131s\u0131yla \u015firketin en zay\u0131f halkas\u0131 buras\u0131. Ancak Signal\u2019in buna kar\u015f\u0131 da \u00f6nlemleri var.<\/p>\n<p>Uygulama, Kay\u0131t Kilidi ad\u0131 verilen bir \u00f6zellik i\u00e7eriyor (etkinle\u015ftirmek i\u00e7in <em>Ayarlar \u2192 Hesap \u2192 Kay\u0131t Kilidi<\/em>). Bu \u00f6zellik etkinle\u015ftirildi\u011finde Signal\u2019i yeni bir cihazda a\u00e7mak i\u00e7in kullan\u0131c\u0131n\u0131n tan\u0131mlad\u0131\u011f\u0131 bir <a href=\"https:\/\/support.signal.org\/hc\/en-us\/articles\/360007059792\" target=\"_blank\" rel=\"noopener nofollow\">PIN<\/a> girilmesi gerekiyor. Bu arada \u015funa da a\u00e7\u0131kl\u0131k getirelim: Signal\u2019deki PIN\u2019in uygulaman\u0131n ekran\u0131n\u0131 a\u00e7makla bir ilgisi yok. Uygulaman\u0131n ekran\u0131, ak\u0131ll\u0131 telefonunuzun ekran\u0131n\u0131 a\u00e7mak i\u00e7in kulland\u0131\u011f\u0131n\u0131z yolla a\u00e7\u0131l\u0131yor.<\/p>\n<div id=\"attachment_10956\" style=\"width: 1034px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-10956\" class=\"wp-image-10956 size-large\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/91\/2022\/08\/29121618\/signal-hacked-but-still-secure-registration-lock-TR-1024x1024.png\" alt=\"\" width=\"1024\" height=\"1024\"><p id=\"caption-attachment-10956\" class=\"wp-caption-text\">Signal ayarlar\u0131nda Kay\u0131t Kilidi<\/p><\/div>\n<p>\u00a0<\/p>\n<p>Kay\u0131t Kilidi varsay\u0131lan olarak devre d\u0131\u015f\u0131 geliyor. Hacklenen hesaplardan en az birinde de devre d\u0131\u015f\u0131yd\u0131. Dolay\u0131s\u0131yla siber su\u00e7lular yakla\u015f\u0131k 13 saat boyunca sald\u0131r\u0131n\u0131n kurban\u0131n\u0131 taklit ederek sald\u0131r\u0131y\u0131 ger\u00e7ekle\u015ftirmeyi ba\u015fard\u0131. <strong>Kay\u0131t Kilidi etkinle\u015ftirilmi\u015f olsayd\u0131 yaln\u0131zca telefon numaras\u0131 ve do\u011frulama kodunu \u00f6\u011frenerek uygulamaya giri\u015f yapamayacaklard\u0131<\/strong>.<\/p>\n<h2>Mesajlar\u0131 daha iyi korumak i\u00e7in neler yap\u0131labilir?<\/h2>\n<p>\u00d6zetlemek gerekirse: Sald\u0131rganlar Signal\u2019in kendisine de\u011fil, i\u015f orta\u011f\u0131 Twilio\u2019ya sald\u0131rd\u0131. Bu yolla 1900 hesaba eri\u015fim elde ettikten sonra i\u00e7lerinden \u00fc\u00e7 tanesine giri\u015f yapt\u0131lar. Dahas\u0131, ne yaz\u0131\u015fmalara ne de rehberdeki ki\u015filere eri\u015fim sa\u011flayabildiler, sadece s\u0131zabildikleri hesaplar\u0131n sahiplerini taklit etmeye \u00e7al\u0131\u015ft\u0131lar. Bu kullan\u0131c\u0131lar Kay\u0131t Kilidi \u00f6zelli\u011fini etkinle\u015ftirmi\u015f olsayd\u0131 bunu bile yapamayacaklard\u0131.<\/p>\n<p>Sald\u0131r\u0131 ka\u011f\u0131t \u00fcst\u00fcnde ba\u015far\u0131l\u0131 olsa da korkuya kap\u0131l\u0131p Signal\u2019i kullanmay\u0131 b\u0131rakmak i\u00e7in hi\u00e7bir sebep yok. Signal, bu hackleme olay\u0131n\u0131n da g\u00f6sterdi\u011fi gibi hala mesajlar\u0131n\u0131z\u0131n gizlili\u011fini sa\u011flayan olduk\u00e7a g\u00fcvenli bir uygulama. Fakat daha da g\u00fcvenli hale getirmeniz m\u00fcmk\u00fcn:<\/p>\n<ul>\n<li>Signal ayarlar\u0131ndan Kay\u0131t Kilidi \u00f6zelli\u011fini etkinle\u015ftirin. Bu sayede siber su\u00e7lular Signal\u2019i yeni bir cihazda etkinle\u015ftirmek i\u00e7in gereken tek seferlik kodu ele ge\u00e7irse bile \u00f6zel PIN\u2019inizi \u00f6\u011frenmeden hesab\u0131n\u0131za giri\u015f yapamaz.<\/li>\n<li><a href=\"https:\/\/www.kaspersky.com.tr\/blog\/signal-privacy-security\/9805\/\" target=\"_blank\" rel=\"noopener\">Signal\u2019deki gizlilik ve g\u00fcvenlik ayarlar\u0131na dair blog yaz\u0131m\u0131z\u0131<\/a> okuyarak uygulaman\u0131z\u0131 yap\u0131land\u0131r\u0131n. Signal hem temel ayarlara hem de ger\u00e7ekten paranoyak olanlara y\u00f6nelik, kullan\u0131labilirlikten \u00f6d\u00fcn verme pahas\u0131na ekstra g\u00fcvenlik sa\u011flayan se\u00e7eneklere sahip.<\/li>\n<li>Bir de elbette ak\u0131ll\u0131 telefonunuza <a href=\"https:\/\/www.kaspersky.com.tr\/mobile-security?icid=tr_kdailyplacehold_acq_ona_smm__onl_b2c_kdaily_wpplaceholder_sm-team___kisa____c8090141bf3f79f6\" target=\"_blank\" rel=\"noopener\">bir g\u00fcvenlik uygulamas\u0131<\/a> y\u00fckleyin. K\u00f6t\u00fc ama\u00e7l\u0131 bir yaz\u0131l\u0131m cihaz\u0131n\u0131za girdi\u011fi takdirde Signal taraf\u0131ndaki hi\u00e7bir g\u00fcvenlik \u00f6nlemi mesajlar\u0131n\u0131z\u0131 ve rehberinizi koruyamaz. Fakat cihaz\u0131n\u0131za k\u00f6t\u00fc ama\u00e7l\u0131 yaz\u0131l\u0131m giremezse ya da en az\u0131ndan zaman\u0131nda yakalan\u0131rsa verilerinize y\u00f6nelik herhangi bir tehdit kalmaz.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kisa-generic-2\">\n","protected":false},"excerpt":{"rendered":"<p>Signal mesajla\u015fma uygulamas\u0131n\u0131n kullan\u0131c\u0131lar\u0131 bir hacker sald\u0131r\u0131s\u0131na u\u011frad\u0131. Olup bitenleri ve sald\u0131r\u0131n\u0131n neden Signal&#8217;in g\u00fcvenilirli\u011fini g\u00f6sterdi\u011fini analiz ediyoruz.<\/p>\n","protected":false},"author":696,"featured_media":10957,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[994],"tags":[2277,500,691,2442,2220],"class_list":{"0":"post-10955","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"tag-e2e","9":"tag-gizlilik","10":"tag-mesajlasma-uygulamalari","11":"tag-signal","12":"tag-uctan-uca-sifreleme"},"hreflang":[{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/signal-hacked-but-still-secure\/10955\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/signal-hacked-but-still-secure\/24504\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/signal-hacked-but-still-secure\/19970\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/signal-hacked-but-still-secure\/10088\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/signal-hacked-but-still-secure\/26949\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/signal-hacked-but-still-secure\/24864\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/signal-hacked-but-still-secure\/25198\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/signal-hacked-but-still-secure\/27525\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/signal-hacked-but-still-secure\/27178\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/signal-hacked-but-still-secure\/33862\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/signal-hacked-but-still-secure\/45273\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/signal-hacked-but-still-secure\/19311\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/signal-hacked-but-still-secure\/19942\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/signal-hacked-but-still-secure\/29177\/"},{"hreflang":"nl","url":"https:\/\/www.kaspersky.nl\/blog\/signal-hacked-but-still-secure\/28431\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/signal-hacked-but-still-secure\/25356\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/signal-hacked-but-still-secure\/30913\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/signal-hacked-but-still-secure\/30617\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.tr\/blog\/tag\/mesajlasma-uygulamalari\/","name":"mesajla\u015fma uygulamalar\u0131"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/10955","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/users\/696"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=10955"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/10955\/revisions"}],"predecessor-version":[{"id":10958,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/posts\/10955\/revisions\/10958"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media\/10957"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=10955"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=10955"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=10955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}