{"id":148408,"date":"2025-11-14T17:12:26","date_gmt":"2025-11-14T15:12:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android"},"modified":"2025-11-14T17:12:26","modified_gmt":"2025-11-14T15:12:29","slug":"rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pt\/blog\/news\/rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android","title":{"rendered":"Rust ultrapassou C\/C++ em termos de c\u00f3digo adicionado \u00e0 plataforma Android","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A Google concluiu uma an\u00e1lise sobre o uso de componentes em Rust na plataforma Android. A estrat\u00e9gia de implementar m\u00e9todos de desenvolvimento seguro no Android para novos c\u00f3digos foi bem-sucedida. Em 2025, pela primeira vez, a propor\u00e7\u00e3o de vulnerabilidades causadas por erros de manipula\u00e7\u00e3o de mem\u00f3ria ficou abaixo de 20% do total de vulnerabilidades. Para compara\u00e7\u00e3o, em 2024, esse n\u00famero era de 24%, enquanto em 2019 era de 76%. O \u00edndice m\u00e9dio da ind\u00fastria continua a ser de 70%.
<\/center> <\/p>\n
O uso de c\u00f3digo em Rust no desenvolvimento de componentes do Android come\u00e7ou em 2020. Em 2025, o volume de novo c\u00f3digo em Rust no Android superou o volume de c\u00f3digo C e C++ adicionado ao longo do ano.
<\/center> <\/p>\n
As estat\u00edsticas acumuladas confirmam a hip\u00f3tese anteriormente expressa de que a principal fonte de problemas de seguran\u00e7a \u00e9 o c\u00f3digo novo, enquanto para o c\u00f3digo antigo observa-se uma depend\u00eancia exponencial da seguran\u00e7a ao longo do tempo \u2014 com o passar do tempo, erros no c\u00f3digo antigo s\u00e3o identificados com menos frequ\u00eancia. No final das contas, a Google decidiu n\u00e3o tentar reescrever o c\u00f3digo antigo em linguagens que manipulam mem\u00f3ria de forma segura, mas se concentrar no uso de tais linguagens para o novo c\u00f3digo. <\/p>\n
Al\u00e9m da seguran\u00e7a, a implementa\u00e7\u00e3o do Rust teve um impacto positivo na velocidade, produtividade e qualidade do desenvolvimento. O c\u00f3digo em Rust registrou quatro vezes menos rollback de altera\u00e7\u00f5es devido \u00e0 identifica\u00e7\u00e3o de erros imprevistos, al\u00e9m de uma redu\u00e7\u00e3o no tempo de revis\u00e3o em 25%.
<\/center>
<\/center> <\/p>\n
Ao implementar mudan\u00e7as de tamanho compar\u00e1vel no Android, as altera\u00e7\u00f5es em Rust exigem aproximadamente 20% menos revis\u00f5es do que seus equivalentes em C++.
<\/center> <\/p>\n
Esses indicadores s\u00e3o explicados pela simplifica\u00e7\u00e3o dos testes e pelo deslocamento da identifica\u00e7\u00e3o de erros para as fases iniciais do desenvolvimento, onde os erros se tornam percept\u00edveis antes mesmo de o desenvolvedor come\u00e7ar a revisar o c\u00f3digo. Al\u00e9m disso, gra\u00e7as \u00e0 elimina\u00e7\u00e3o das sobrecargas de isolamento sandbox no c\u00f3digo em Rust, foi poss\u00edvel obter um aumento de desempenho. <\/p>\n
Recent projects involving the use of Rust in Android have highlighted the deployment of the first widely used driver in Rust within the Linux kernel 6.12, as well as the use of Rust in the development of firmware and application software. In addition to the driver already implemented in the kernel, a new GPU driver is being developed in collaboration with ARM and Collabora using this language. The Nearby Presence protocol, implemented in Rust and used in Google Play Services, enables the discovery of local devices via Bluetooth. A new implementation of the MLS protocol, written in Rust, is planned for inclusion in the next release of the Google Messages app. The Chromium browser engine employs Rust-written parsers for web fonts, PNG images, and the JSON format. <\/p>\n
Currently, there are about 5 million lines of Rust code in Android, with only one potential vulnerability identified, caused by memory management issues. This results in a vulnerability density of 0.2 vulnerabilities per million lines of Rust code. In contrast, the figure for C and C++ code is around 1000 vulnerabilities per million lines. The main source of problems in Rust arises from code located in unsafe blocks, which constitutes about 4% of all Rust code. <\/p>\n
The aforementioned vulnerability CVE-2025-48530 was found in the Crabby Avif library, which includes a parser and decoder for the Avif format. The issue was identified by Google employees before the release and did not affect users. This vulnerability was caused by an error in an unsafe block that led to a buffer overflow. It is noted that even if the error had gone unnoticed, its exploitation would have been blocked by the Scudo memory distribution system included in Android, which is by default activated in firmware for Google Pixel and some other devices. \n Fonte: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Rust](\"\/wp-content\/uploads\/2025\/11\/a0d9be55320372c273ae9ab866bd931a.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/e037910fecc720718e226738cedeb152.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/b48c4e42b79406f455f1e88fd1192ef7.png\")
<\/center> ![\"Rust](\"\/wp-content\/uploads\/2025\/11\/45a95cc5ff7dfd12e5dd14de43129347.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/8a6c77a11aafcc95872ed06fc54f1265.png\")
<\/center> <\/p>\n