[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[DONE] wml://{security/2018/dsa-4103.wml}

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- --- english/security/2018/dsa-4103.wml	2018-02-01 12:26:02.267832237 +0500
+++ russian/security/2018/dsa-4103.wml	2018-02-01 13:31:13.823920629 +0500
@@ -1,126 +1,127 @@
- -<define-tag description>security update</define-tag>
+#use wml::debian::translation-check translation="1.2" maintainer="Lev Lamberov"
+<define-tag description>обновление безопаÑ?ноÑ?Ñ?и</define-tag>
 <define-tag moreinfo>
- -<p>Several vulnerabilities have been discovered in the chromium web browser.</p>
+<p>Ð? веб-бÑ?аÑ?зеÑ?е chromium бÑ?ло обнаÑ?Ñ?жено неÑ?колÑ?ко Ñ?Ñ?звимоÑ?Ñ?ей.</p>
 
 <ul>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15420";>CVE-2017-15420</a>
 
- -    <p>Drew Springall discovered a URL spoofing issue.</p></li>
+    <p>Ð?Ñ?Ñ? СпÑ?ингол обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? подделки URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2017-15429";>CVE-2017-15429</a>
 
- -    <p>A cross-site scripting issue was discovered in the v8 javascript
- -    library.</p></li>
+    <p>Ð? javascript-библиоÑ?еке v8 бÑ?л обнаÑ?Ñ?жен межÑ?айÑ?овÑ?й
+    Ñ?кÑ?ипÑ?инг.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6031";>CVE-2018-6031</a>
 
- -    <p>A use-after-free issue was discovered in the pdfium library.</p></li>
+    <p>Ð?Ñ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и бÑ?ло обнаÑ?Ñ?жено в библиоÑ?еке pdfium.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6032";>CVE-2018-6032</a>
 
- -    <p>Jun Kokatsu discovered a way to bypass the same origin policy.</p></li>
+    <p>Ð?жÑ?н Ð?окаÑ?Ñ?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об обÑ?ода пÑ?авила одного иÑ?Ñ?оÑ?ника.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6033";>CVE-2018-6033</a>
 
- -    <p>Juho Nurminen discovered a race condition when opening downloaded
- -    files.</p></li>
+    <p>ЮÑ?о Ð?Ñ?Ñ?минен обнаÑ?Ñ?жил Ñ?оÑ?Ñ?оÑ?ние гонки пÑ?и оÑ?кÑ?Ñ?Ñ?ии загÑ?Ñ?женнÑ?Ñ?
+    Ñ?айлов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6034";>CVE-2018-6034</a>
 
- -    <p>Tobias Klein discovered an integer overflow issue.</p></li>
+    <p>ТобиаÑ? Ð?лÑ?йн обнаÑ?Ñ?жил пеÑ?еполнение Ñ?елÑ?Ñ? Ñ?иÑ?ел.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6035";>CVE-2018-6035</a>
 
- -    <p>Rob Wu discovered a way for extensions to access devtools.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об, Ñ? помоÑ?Ñ?Ñ? коÑ?оÑ?ого Ñ?аÑ?Ñ?иÑ?ениÑ? могÑ?Ñ? полÑ?Ñ?иÑ?Ñ? доÑ?Ñ?Ñ?п к инÑ?Ñ?Ñ?Ñ?менÑ?ам Ñ?азÑ?абоÑ?Ñ?ика.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6036";>CVE-2018-6036</a>
 
- -    <p>UK's National Cyper Security Centre discovered an integer overflow
- -    issue.</p></li>
+    <p>СоÑ?Ñ?Ñ?дники Ð?аÑ?ионалÑ?ного Ñ?енÑ?Ñ?а кибеÑ?безопаÑ?ноÑ?Ñ?и Ð?еликобÑ?иÑ?ании обнаÑ?Ñ?жили пеÑ?еполнение
+    Ñ?елÑ?Ñ? Ñ?иÑ?ел.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6037";>CVE-2018-6037</a>
 
- -    <p>Paul Stone discovered an issue in the autofill feature.</p></li>
+    <p>Ð?ол СÑ?оÑ?н обнаÑ?Ñ?жил пÑ?облемÑ? в инÑ?Ñ?Ñ?Ñ?менÑ?е авÑ?озаполнениÑ? Ñ?оÑ?м.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6038";>CVE-2018-6038</a>
 
- -    <p>cloudfuzzer discovered a buffer overflow issue.</p></li>
+    <p>cloudfuzzer обнаÑ?Ñ?жил пеÑ?еполнение бÑ?Ñ?еÑ?а.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6039";>CVE-2018-6039</a>
 
- -    <p>Juho Nurminen discovered a cross-site scripting issue in the
- -    developer tools.</p></li>
+    <p>ЮÑ?о Ð?Ñ?Ñ?минен обнаÑ?Ñ?жил межÑ?айÑ?овÑ?й Ñ?кÑ?ипÑ?инг в инÑ?Ñ?Ñ?Ñ?менÑ?аÑ?
+    Ñ?азÑ?абоÑ?Ñ?ика.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6040";>CVE-2018-6040</a>
 
- -    <p>WenXu Wu discovered a way to bypass the content security policy.</p></li>
+    <p>Ð?Ñ?нÑ?СÑ?й Ð?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об обÑ?ода пÑ?авила безопаÑ?ноÑ?Ñ?и Ñ?одеÑ?жимого.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6041";>CVE-2018-6041</a>
 
- -    <p>Luan Herrera discovered a URL spoofing issue.</p></li>
+    <p>Ð?Ñ?ан Ð?еÑ?Ñ?еÑ?а обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? подделки URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6042";>CVE-2018-6042</a>
 
- -    <p>Khalil Zhani discovered a URL spoofing issue.</p></li>
+    <p>Халил Ð?ани обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? подделки URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6043";>CVE-2018-6043</a>
 
- -    <p>A character escaping issue was discovered.</p></li>
+    <p>Ð?Ñ?ла обнаÑ?Ñ?жена пÑ?облема Ñ? Ñ?кÑ?аниÑ?ованием Ñ?имволов.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6045";>CVE-2018-6045</a>
 
- -    <p>Rob Wu discovered a way for extensions to access devtools.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об, Ñ? помоÑ?Ñ?Ñ? коÑ?оÑ?ого Ñ?аÑ?Ñ?иÑ?ениÑ? могÑ?Ñ? полÑ?Ñ?иÑ?Ñ? доÑ?Ñ?Ñ?п к инÑ?Ñ?Ñ?Ñ?менÑ?ам Ñ?азÑ?абоÑ?Ñ?ика.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6046";>CVE-2018-6046</a>
 
- -    <p>Rob Wu discovered a way for extensions to access devtools.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об, Ñ? помоÑ?Ñ?Ñ? коÑ?оÑ?ого Ñ?аÑ?Ñ?иÑ?ениÑ? могÑ?Ñ? полÑ?Ñ?иÑ?Ñ? доÑ?Ñ?Ñ?п к инÑ?Ñ?Ñ?Ñ?менÑ?ам Ñ?азÑ?абоÑ?Ñ?ика.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6047";>CVE-2018-6047</a>
 
- -    <p>Masato Kinugawa discovered an information leak issue.</p></li>
+    <p>Ð?аÑ?аÑ?о Ð?инÑ?гава обнаÑ?Ñ?жил Ñ?Ñ?еÑ?кÑ? инÑ?оÑ?маÑ?ии.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6048";>CVE-2018-6048</a>
 
- -    <p>Jun Kokatsu discoverd a way to bypass the referrer policy.</p></li>
+    <p>Ð?жÑ?н Ð?окаÑ?Ñ?Ñ? обнаÑ?Ñ?жил Ñ?поÑ?об обÑ?ода пÑ?авила Ñ?Ñ?Ñ?лаÑ?Ñ?егоÑ?Ñ? домена.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6049";>CVE-2018-6049</a>
 
- -    <p>WenXu Wu discovered a user interface spoofing issue.</p></li>
+    <p>Ð?Ñ?нÑ?СÑ?й Ð?Ñ? обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? подделки полÑ?зоваÑ?елÑ?Ñ?кого инÑ?еÑ?Ñ?ейÑ?а.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6050";>CVE-2018-6050</a>
 
- -    <p>Jonathan Kew discovered a URL spoofing issue.</p></li>
+    <p>Ð?жонаÑ?ан Ð?Ñ?Ñ? обнаÑ?Ñ?жил возможноÑ?Ñ?Ñ? подделки URL.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6051";>CVE-2018-6051</a>
 
- -    <p>Anonio Sanso discovered an information leak issue.</p></li>
+    <p>Ð?нÑ?онио СанÑ?о обнаÑ?Ñ?жил Ñ?Ñ?еÑ?кÑ? инÑ?оÑ?маÑ?ии.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6052";>CVE-2018-6052</a>
 
- -    <p>Tanner Emek discovered that the referrer policy implementation
- -    was incomplete.</p></li>
+    <p>ТаннеÑ? Эмек обнаÑ?Ñ?жил, Ñ?Ñ?о Ñ?еализаÑ?иÑ? пÑ?авила Ñ?Ñ?Ñ?лаÑ?Ñ?егоÑ?Ñ? домена Ñ?влÑ?еÑ?Ñ?Ñ?
+    неполной.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6053";>CVE-2018-6053</a>
 
- -    <p>Asset Kabdenov discovered an information leak issue.</p></li>
+    <p>Ð?Ñ?еÑ? Ð?абденов обнаÑ?Ñ?жил Ñ?Ñ?еÑ?кÑ? инÑ?оÑ?маÑ?ии.</p></li>
 
 <li><a href="https://security-tracker.debian.org/tracker/CVE-2018-6054";>CVE-2018-6054</a>
 
- -    <p>Rob Wu discovered a use-after-free issue.</p></li>
+    <p>Роб Ð?Ñ? обнаÑ?Ñ?жил иÑ?полÑ?зование Ñ?казаÑ?елей поÑ?ле оÑ?вобождениÑ? памÑ?Ñ?и.</p></li>
 
 </ul>
 
- -<p>For the oldstable distribution (jessie), security support for chromium
- -has been discontinued.</p>
+<p>Ð? пÑ?едÑ?дÑ?Ñ?ем Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (jessie) поддеÑ?ка безопаÑ?ноÑ?Ñ?и chromium
+бÑ?ла пÑ?екÑ?аÑ?ена.</p>
 
- -<p>For the stable distribution (stretch), these problems have been fixed in
- -version 64.0.3282.119-1~deb9u1.</p>
+<p>Ð? Ñ?Ñ?абилÑ?ном вÑ?пÑ?Ñ?ке (stretch) Ñ?Ñ?и пÑ?облемÑ? бÑ?ли иÑ?пÑ?авленÑ? в
+веÑ?Ñ?ии 64.0.3282.119-1~deb9u1.</p>
 
- -<p>We recommend that you upgrade your chromium-browser packages.</p>
+<p>РекомендÑ?еÑ?Ñ?Ñ? обновиÑ?Ñ? пакеÑ?Ñ? chromium-browser.</p>
 
- -<p>For the detailed security status of chromium-browser please refer to
- -its security tracker page at:
+<p>С подÑ?обнÑ?м Ñ?Ñ?аÑ?Ñ?Ñ?ом поддеÑ?жки безопаÑ?ноÑ?Ñ?и chromium-browser можно ознакомиÑ?Ñ?Ñ?Ñ? на
+Ñ?ооÑ?веÑ?Ñ?Ñ?вÑ?Ñ?Ñ?ей Ñ?Ñ?Ñ?аниÑ?е оÑ?Ñ?леживаниÑ? безопаÑ?ноÑ?Ñ?и по адÑ?еÑ?Ñ?
 <a href="https://security-tracker.debian.org/tracker/chromium-browser";>\
 https://security-tracker.debian.org/tracker/chromium-browser</a></p>
 </define-tag>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAlpy0HIACgkQXudu4gIW
0qVowg/5AYobspp7qPn4d3kVdlo9aJg7JuH1u4+KBBbPuRYvpn4Bxgft8z7walJa
8n8K2WckEFAIVcGfbEaI49j0s88h6kVfARBU1H9A0En/yhcGVa7kJ4PmlQoaiqDQ
YAVtp2wdjHm2Kuertdo/4F7P5r66eVikIGHoCCtF02ZgCxoopBbx0lvNbMxXfjxD
s8klMQ2AvaCjKqgrp+u+wOH6XFiCsNMSugCyWfOnhUW/lDhXmCUfnlBl37mwK4Wu
mNVNLXwoE0w1yt3QzndaMaJUEFtEu98820Ys4/Gy6gf2z/xLs2D5Fg1iDsDYrx7h
jh343rzBbsG+S3C9i4WUmLeytsXz268T9WkIxPqR/M8NeCbwrnKskRSIsZlmyc5H
sNchkVkFe6tp4aOB9Ex3kOCUfpr0kUUL1ZPxOVqWzY1TJ405g8DI1Z84ha1wmXwN
B6lXP/Tffpf2HgaU5OuNAhbVz2CDV5Zalu8YSNq52vshwMMMsCoIh4e0FJOiiITl
exH45soWT/3LiKsOOMTTnjypaP1Bxjw4smqpbOYBpVVgx+rfgvjls2PVUIaq9EVv
pYnFLbR2f6OG76SjWl0oyO9qNpdegMd6j9sWSBguFDqr1fGR7B7G49EgkolIUP3q
Y6wbDp3x7vRSI2EMUNoo/73PXfGKpuYJyNzxpcJgGvhlsDRgVFY=
=bAZd
-----END PGP SIGNATURE-----
Reply to: