{"id":2805,"date":"2026-04-20T09:27:19","date_gmt":"2026-04-20T09:27:19","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-04-20T09:27:20","modified_gmt":"2026-04-20T09:27:20","slug":"cups-rce-pe-vps-linux-cve-2026-34980-se-inlantuie-pana-la-root-verifica-daca-esti-expus-chiar-acum","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/cups-rce-pe-vps-linux-cve-2026-34980-se-inlantuie-pana-la-root-verifica-daca-esti-expus-chiar-acum\/","title":{"rendered":"CUPS RCE pe VPS Linux: CVE-2026-34980 se \u00eenl\u0103n\u021buie p\u00e2n\u0103 la root \u2014 verific\u0103 dac\u0103 e\u0219ti expus chiar acum"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Dou\u0103 vulnerabilit\u0103\u021bi publicate pe 2 aprilie 2026 \u2014 CVE-2026-34980 \u0219i CVE-2026-34990 \u2014 se \u00eenl\u0103n\u021buie \u00eentr-un exploit complet neautentificat, de la acces de re\u021bea la root, \u00eempotriva oric\u0103rui server Linux care ruleaz\u0103 CUPS cu o coad\u0103 PostScript partajat\u0103 accesibil\u0103 \u00een re\u021bea. Exploatarea activ\u0103 a fost confirmat\u0103. Remedierea este un singur r\u00e2nd de comand\u0103 dac\u0103 nu imprimai nimic, respectiv un singur upgrade de pachet dac\u0103 imprima\u021bi. Ruleaz\u0103 verificarea de mai jos imediat, \u00eenainte de a citi restul.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl is-active cups 2&gt;\/dev\/null || echo \"CUPS not running\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 rezultatul este <code>active<\/code>, serverul t\u0103u este expus p\u00e2n\u0103 c\u00e2nd iei m\u0103suri. Dac\u0103 returneaz\u0103 <code>inactive<\/code>, <code>unknown<\/code> sau <code>CUPS not running<\/code>, nu e\u0219ti expus imediat vectorului de re\u021bea \u2014 dar verific\u0103 dac\u0103 pachetul este instalat, deoarece CVE-2026-34990 are o cale de escaladare local\u0103 a privilegiilor care conteaz\u0103 chiar \u0219i dac\u0103 serviciul este oprit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De ce serverele VPS sunt \u021binta principal\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CUPS nu a fost conceput pentru medii server. Este un subsistem desktop de imprimare. Problema este c\u0103 multe imagini de baz\u0103 ale distribu\u021biilor \u2014 inclusiv cele folosite pentru templateurile VPS \u2014 instaleaz\u0103 CUPS ca dependen\u021b\u0103 recomandat\u0103 a altor pachete, adesea f\u0103r\u0103 nicio solicitare explicit\u0103 din partea operatorului. Un sistem Rocky Linux sau Ubuntu Server provizionat dintr-o imagine standard poate avea <code>cupsd<\/code> rul\u00e2nd pe portul 631, ascult\u00e2nd conexiuni, de\u0219i acel VPS nu a v\u0103zut niciodat\u0103 o imprimant\u0103 \u00een toat\u0103 existen\u021ba sa.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este suprafa\u021ba de atac care face CVE-2026-34980 dispropor\u021bionat de periculos pentru infrastructura cloud fa\u021b\u0103 de sistemele desktop. Pe un desktop, CUPS este de a\u0219teptat s\u0103 fie prezent, iar un firewall local blocheaz\u0103 de obicei portul 631 de la accesul extern. Pe un VPS, acela\u0219i port este adesea deschis spre internet pentru c\u0103 nimeni nu s-a g\u00e2ndit s\u0103 auditeze un daemon de imprimare pe un server web. Conform cercet\u0103torului care a descoperit lan\u021bul de exploatare, condi\u021biile necesare \u2014 un cupsd expus \u00een re\u021bea cu o coad\u0103 PostScript partajat\u0103 \u2014 sunt \u00eendeplinite \u00een practic\u0103 pe o propor\u021bie mare din serverele Linux scanate \u00een perioada de dezv\u0103luire responsabil\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cum func\u021bioneaz\u0103 lan\u021bul celor dou\u0103 CVE-uri<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen\u021belegerea mecanismului conteaz\u0103 deoarece determin\u0103 ce m\u0103sur\u0103 de remediere se aplic\u0103 situa\u021biei tale. Cele dou\u0103 vulnerabilit\u0103\u021bi sunt independente la nivel de cod, dar secven\u021biale \u00een calea de atac.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CVE-2026-34980 \u2014 RCE neautentificat ca utilizator lp<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">CUPS accept\u0103 implicit cereri anonime de tip Print-Job pentru cozile partajate \u2014 verificarea autentific\u0103rii blocheaz\u0103 doar joburile de la distan\u021b\u0103 c\u0103tre cozile nepartajate. Vulnerabilitatea este o eroare de parsare \u00een modul \u00een care <code>cupsd<\/code> gestioneaz\u0103 valoarea op\u021biunii <code>page-border<\/code> transmis\u0103 ca <code>textWithoutLanguage<\/code> \u00eentr-o cerere IPP construit\u0103 mali\u021bios. Un atacator injecteaz\u0103 un caracter de linie nou\u0103 \u00een interiorul valorii op\u021biunii. CUPS p\u0103streaz\u0103 linia nou\u0103 prin etapa de escapare \u0219i re-parsare a op\u021biunilor, iar linia rezultat\u0103 este interpretat\u0103 ca o \u00eenregistrare de control de tip PPD a schedulerului \u2014 provenind dintr-o surs\u0103 de \u00eencredere \u2014 \u00een loc de date furnizate de utilizator.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un job de imprimare raw ulterior exploateaz\u0103 \u00eenregistrarea de control injectat\u0103 pentru a instrui schedulerul s\u0103 execute un binar existent pe server. Atacatorul ob\u021bine execu\u021bie de cod ca contul de serviciu <code>lp<\/code>. Prin el \u00eensu\u0219i, acesta este un risc serios, dar nu decisiv \u2014 <code>lp<\/code> este un cont cu privilegii reduse \u0219i nu poate citi direct fi\u0219iere sensibile sau scrie \u00een c\u0103ile de sistem. Aici intr\u0103 al doilea CVE.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CVE-2026-34990 \u2014 de la lp la root prin abuzul tokenului IPP de pe localhost<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Al doilea defect exist\u0103 \u00een politica de autorizare implicit\u0103 CUPS pentru conexiunile de pe localhost. CUPS emite tokenuri reutilizabile <code>Authorization: Local<\/code> pentru conexiunile locale \u0219i \u2014 critic \u2014 opera\u021biunea IPP <code>CUPS-Create-Local-Printer<\/code> nu este restric\u021bionat\u0103 prin autentificare de administrator atunci c\u00e2nd cererea provine de pe localhost \u00een politica implicit\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cu execu\u021bie de cod ca <code>lp<\/code>, atacatorul for\u021beaz\u0103 <code>cupsd<\/code> s\u0103 se autentifice la un serviciu IPP controlat de atacator pe un port ales de localhost. CUPS transmite un token local. Atacatorul reutilizeaz\u0103 acel token pentru a emite cereri directe c\u0103tre <code>\/admin\/<\/code> \u00eempotriva instan\u021bei cupsd active. Folosind <code>CUPS-Create-Local-Printer<\/code> cu <code>printer-is-shared=true<\/code> \u0219i un URI <code>file:\/\/\/<\/code>, atacatorul \u00eenregistreaz\u0103 o imprimant\u0103 fals\u0103 care pointeaz\u0103 c\u0103tre orice cale de fi\u0219ier din sistem. Politica normal\u0103 <code>FileDevice<\/code> respinge URI-urile <code>file:\/\/<\/code>, dar acest bypass ocole\u0219te restric\u021bia prin calea <code>Create-Local-Printer<\/code>. Declan\u0219area unui job de imprimare c\u0103tre acea imprimant\u0103 fals\u0103 produce o suprascriere arbitrar\u0103 de fi\u0219ier ca root. Dovada de concept publicat\u0103 scrie un fragment sudoers care acord\u0103 atacatorului execu\u021bie complet\u0103 de comenzi ca root.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Lan\u021bul complet: atacator de re\u021bea neautentificat \u2192 job IPP de imprimare \u2192 RCE ca lp \u2192 capturare token localhost \u2192 acces API admin \u2192 suprascriere fi\u0219ier ca root \u2192 intrare sudoers \u2192 shell root. Nicio creden\u021bial\u0103 nu este necesar\u0103 \u00een nicio etap\u0103 a intr\u0103rii ini\u021biale.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Versiuni afectate \u0219i starea patch-urilor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ambele CVE-uri afecteaz\u0103 CUPS versiunea 2.4.16 \u0219i anterioare. OpenPrinting a lansat <strong>CUPS 2.4.17<\/strong> pe 16 aprilie 2026, care remediaz\u0103 CVE-2026-34980 (filtrarea caracterelor de control \u00een valorile op\u021biunilor) \u0219i CVE-2026-34990 (gestionarea certificatelor locale pe interfa\u021ba loopback), al\u0103turi de alte patru CVE-uri corectate \u00een aceea\u0219i versiune.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Disponibilitatea patch-urilor la nivel de distribu\u021bie la data de 20 aprilie 2026:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Distribu\u021bie<\/th><th>Status CVE-2026-34980<\/th><th>Status CVE-2026-34990<\/th><th>Ac\u021biune necesar\u0103<\/th><\/tr><\/thead><tbody><tr><td>Ubuntu 22.04 \/ 24.04<\/td><td>Patch \u00een curs<\/td><td>Patch \u00een curs<\/td><td>Dezactiveaz\u0103 sau blocheaz\u0103 portul 631 imediat<\/td><\/tr><tr><td>Debian 11 Bullseye<\/td><td>Vulnerabil (2.3.3op2)<\/td><td>Vulnerabil<\/td><td>Dezactiveaz\u0103 sau blocheaz\u0103 portul 631 imediat<\/td><\/tr><tr><td>Debian 12 Bookworm<\/td><td>Vulnerabil (2.4.2)<\/td><td>Vulnerabil<\/td><td>Dezactiveaz\u0103 sau blocheaz\u0103 portul 631 imediat<\/td><\/tr><tr><td>Rocky Linux 8 \/ 9<\/td><td>Advisory Red Hat activ<\/td><td>Advisory Red Hat activ<\/td><td>Dezactiveaz\u0103 sau aplic\u0103 updateul din advisory<\/td><\/tr><tr><td>AlmaLinux 8 \/ 9<\/td><td>Advisory Red Hat activ<\/td><td>Advisory Red Hat activ<\/td><td>Dezactiveaz\u0103 sau aplic\u0103 updateul din advisory<\/td><\/tr><tr><td>openSUSE \/ SLES<\/td><td>Advisory SUSE activ<\/td><td>Advisory SUSE activ<\/td><td>Aplic\u0103 update de securitate via zypper<\/td><\/tr><tr><td>Arch Linux<\/td><td>cups 2.4.17 \u00een repo<\/td><td>cups 2.4.17 \u00een repo<\/td><td><code>pacman -Syu<\/code><\/td><\/tr><tr><td>Alpine Linux<\/td><td>Verific\u0103 tracker-ul aports<\/td><td>Verific\u0103 tracker-ul aports<\/td><td>Dezactiveaz\u0103 sau <code>apk upgrade cups<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru distribu\u021biile unde pachetul corectat nu este \u00eenc\u0103 disponibil \u00een repo-urile oficiale, dezactivarea complet\u0103 a serviciului este m\u0103sura corect\u0103 \u2014 nu a\u0219teptarea. Un VPS care nu folose\u0219te o imprimant\u0103 nu are niciun motiv s\u0103 ruleze <code>cupsd<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 1 \u2014 Verificare complet\u0103 a expunerii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ruleaz\u0103 acest bloc \u00een consola VPS-ului t\u0103u sau prin SSH. Verific\u0103 dac\u0103 serviciul ruleaz\u0103, ce versiune este instalat\u0103 \u0219i dac\u0103 portul 631 este accesibil din exterior:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Verific\u0103 dac\u0103 cupsd ruleaz\u0103\nsystemctl is-active cups 2&gt;\/dev\/null &amp;&amp; echo \"EXPUS: cupsd este activ\" || echo \"cupsd nu ruleaz\u0103\"\n\n# Verific\u0103 versiunea instalat\u0103\ncups-config --version 2&gt;\/dev\/null || dpkg -l cups 2&gt;\/dev\/null | grep ^ii || rpm -q cups 2&gt;\/dev\/null\n\n# Verific\u0103 dac\u0103 portul 631 ascult\u0103 \u0219i pe ce interfa\u021b\u0103\nss -tlnp | grep 631<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A treia comand\u0103 este cea mai important\u0103. Dac\u0103 portul 631 apare ca <code>0.0.0.0:631<\/code> sau <code>:::631<\/code>, daemonul ascult\u0103 pe toate interfe\u021bele \u0219i este accesibil din internet. Dac\u0103 apare ca <code>127.0.0.1:631<\/code>, vectorul de atac de re\u021bea al CVE-2026-34980 este blocat \u2014 dar calea de escaladare local\u0103 a CVE-2026-34990 r\u0103m\u00e2ne aplicabil\u0103 dac\u0103 exist\u0103 conturi de utilizator local pe ma\u0219in\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2a \u2014 Dac\u0103 VPS-ul t\u0103u nu imprim\u0103 (majoritatea workload-urilor VPS)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Opre\u0219te \u0219i dezactiveaz\u0103 permanent CUPS. Dezactiveaz\u0103 \u0219i <code>cups-browsed<\/code> dac\u0103 este prezent \u2014 este un serviciu separat care particip\u0103 la lan\u021bul de vulnerabilit\u0103\u021bi CUPS din 2024 \u0219i nu are niciun scop pe un server:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Opre\u0219te \u0219i dezactiveaz\u0103 schedulerul principal CUPS\nsystemctl stop cups\nsystemctl disable cups\nsystemctl mask cups\n\n# Opre\u0219te \u0219i dezactiveaz\u0103 cups-browsed dac\u0103 este instalat\nsystemctl stop cups-browsed 2&gt;\/dev\/null\nsystemctl disable cups-browsed 2&gt;\/dev\/null\nsystemctl mask cups-browsed 2&gt;\/dev\/null\n\n# Verific\u0103 c\u0103 ambele sunt oprite\nsystemctl is-active cups cups-browsed 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Comanda <code>mask<\/code> merge mai departe dec\u00e2t <code>disable<\/code> \u2014 creeaz\u0103 un symlink al unit\u0103\u021bii de serviciu c\u0103tre <code>\/dev\/null<\/code>, \u00eempiedic\u00e2nd orice alt pachet sau proces s\u0103 \u00eel porneasc\u0103 ca dependen\u021b\u0103. Pe Alpine Linux (OpenRC), echivalentul este:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rc-service cups stop\nrc-update del cups\nrc-update del cups-browsed 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe FreeBSD, previne pornirea la boot:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sysrc cupsd_enable=\"NO\"\nservice cupsd stop 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 mascare, ruleaz\u0103 din nou blocul de verificare a expunerii \u0219i confirm\u0103 c\u0103 portul 631 nu mai apare \u00een rezultatul <code>ss<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2b \u2014 Dac\u0103 VPS-ul t\u0103u ruleaz\u0103 un server de imprimare (upgrade necesar)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 rulezi CUPS \u00een mod deliberat \u2014 de exemplu, un server de imprimare partajat sau un VPS de tip workstation cu interfa\u021b\u0103 grafic\u0103 \u2014 dezactivarea serviciului nu este o op\u021biune. Ac\u021biunea corect\u0103 este upgrade-ul la CUPS 2.4.17, singura versiune care corecteaz\u0103 ambele CVE-uri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Arch Linux, unde 2.4.17 este deja \u00een repo-uri:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pacman -Syu cups<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe distribu\u021biile unde 2.4.17 nu este \u00eenc\u0103 disponibil prin managerul de pachete al sistemului, aplic\u0103 updateul de securitate disponibil din advisory ca m\u0103sur\u0103 par\u021bial\u0103 \u0219i adaug\u0103 imediat o regul\u0103 de firewall pentru a restric\u021biona portul 631 la adrese IP surs\u0103 de \u00eencredere:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Ubuntu \/ Debian \u2014 blocheaz\u0103 accesul extern la portul CUPS\nufw deny 631\/tcp\nufw deny 631\/udp\nufw reload<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code># Rocky Linux \/ AlmaLinux \/ RHEL\nfirewall-cmd --permanent --remove-service=mdns\nfirewall-cmd --permanent --add-rich-rule='rule family=\"ipv4\" port port=\"631\" protocol=\"tcp\" reject'\nfirewall-cmd --permanent --add-rich-rule='rule family=\"ipv4\" port port=\"631\" protocol=\"udp\" reject'\nfirewall-cmd --reload<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Regula de firewall neutralizeaz\u0103 vectorul de re\u021bea al CVE-2026-34980 f\u0103r\u0103 a dezactiva func\u021bionalitatea de imprimare pentru utilizatorii locali. CVE-2026-34990 r\u0103m\u00e2ne un risc at\u00e2t timp c\u00e2t serviciul ruleaz\u0103 \u0219i conturile neprivilegiate au acces local, deci upgrade-ul la CUPS 2.4.17 r\u0103m\u00e2ne necesar imediat ce pachetul corectat ajunge \u00een repo-ul distribu\u021biei tale.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 3 \u2014 Verificarea remedierii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 aplicarea oric\u0103rei m\u0103suri de remediere, confirm\u0103 starea cu o verificare final\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Confirm\u0103 c\u0103 serviciul nu ruleaz\u0103 (calea de dezactivare)\nsystemctl is-active cups &amp;&amp; echo \"ATEN\u021aIE: \u00eenc\u0103 activ\" || echo \"OK: nu ruleaz\u0103\"\n\n# Confirm\u0103 c\u0103 portul 631 nu mai este expus (ambele c\u0103i)\nss -tlnp | grep 631 &amp;&amp; echo \"ATEN\u021aIE: portul \u00eenc\u0103 deschis\" || echo \"OK: portul 631 nu ascult\u0103\"\n\n# Confirm\u0103 c\u0103 masca este activ\u0103 (calea de dezactivare)\nsystemctl is-enabled cups<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ultima comand\u0103 trebuie s\u0103 returneze <code>masked<\/code>, nu <code>disabled<\/code>. O unitate mascat\u0103 nu poate fi pornit\u0103 de niciun trigger, inclusiv updateuri de pachete. O unitate doar dezactivat\u0103 poate fi pornit\u0103 manual sau ca dependen\u021b\u0103 \u2014 mascarea este starea corect\u0103 pentru un serviciu pe care l-ai eliminat inten\u021bionat de pe un server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Context de hardening mai larg<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Situa\u021bia CUPS este un exemplu specific al unei probleme generale: serviciile care apar\u021bin mediilor workstation ajung pe servere deoarece imaginile de baz\u0103 ale sistemelor de operare sunt construite pentru acoperire larg\u0103, nu pentru suprafa\u021b\u0103 minim\u0103 de atac. Un VPS Ubuntu Server sau Rocky Linux proasp\u0103t instalat poate rula un daemon de imprimare, un responder Avahi mDNS, un stub de stiv\u0103 Bluetooth \u0219i un agent SNMP \u2014 niciunul din ele nu apar\u021bine unui server cloud, toate au un istoric CVE relevant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Practica corect\u0103 pe termen lung este un audit explicit al serviciilor care ruleaz\u0103 imediat dup\u0103 provizionarea unui VPS nou:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl list-units --type=service --state=running<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Orice serviciu pentru care nu po\u021bi explica un motiv specific ar trebui oprit \u0219i mascat. Aceasta aduce VPS-ul la o stare minim\u0103 de rulare unde suprafa\u021ba de atac corespunde workload-ului real, nu ipotezelor implicite ale unui manifest de pachete desktop.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai nevoie de ajutor pentru auditarea \u0219i hardening-ul unui VPS \u2014 inclusiv identificarea serviciilor nea\u0219teptate care ruleaz\u0103, configurarea regulilor de firewall \u0219i aplicarea advisory-urilor de securitate \u00een a\u0219teptare \u2014 <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">serviciul de administrare Linux gestionat ServerSpan<\/a> acoper\u0103 direct aceast\u0103 categorie de lucru. Pentru serverele nou provizionate care au nevoie de un punct de plecare curat, toate <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">planurile VPS ServerSpan<\/a> includ acces root complet \u0219i disponibilitate consol\u0103 astfel \u00eenc\u00e2t s\u0103 po\u021bi aplica ace\u0219ti pa\u0219i imediat dup\u0103 provizionare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Rezumat ac\u021biuni necesare la data de 20 aprilie 2026:<\/strong> Dac\u0103 VPS-ul t\u0103u ruleaz\u0103 CUPS \u0219i nu ai nevoie de el \u2014 opre\u0219te, dezactiveaz\u0103 \u0219i mascheaz\u0103 serviciul chiar acum. Dac\u0103 ai nevoie de CUPS \u0219i e\u0219ti pe Arch Linux, f\u0103 upgrade la 2.4.17 via <code>pacman -Syu<\/code>. Dac\u0103 ai nevoie de CUPS pe orice alt\u0103 distribu\u021bie unde 2.4.17 nu este \u00eenc\u0103 \u00een repo-uri, adaug\u0103 o regul\u0103 de firewall care blocheaz\u0103 portul 631 extern \u0219i urm\u0103re\u0219te apari\u021bia pachetului corectat. Niciun patch, nicio excep\u021bie \u2014 CVE-2026-34990 acord\u0103 root oric\u0103rui utilizator local pe o configura\u021bie CUPS implicit\u0103.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Dou\u0103 vulnerabilit\u0103\u021bi publicate pe 2 aprilie 2026 \u2014 CVE-2026-34980 \u0219i CVE-2026-34990 \u2014 se \u00eenl\u0103n\u021buie \u00eentr-un exploit complet neautentificat, de la acces de re\u021bea la root, \u00eempotriva oric\u0103rui server Linux care ruleaz\u0103 CUPS cu o coad\u0103 PostScript partajat\u0103 accesibil\u0103 \u00een re\u021bea. Exploatarea activ\u0103 a fost confirmat\u0103. Remedierea este un singur r\u00e2nd de comand\u0103 dac\u0103 nu imprimai [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2803,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[15757,15752,15749,15736,15742,15750,15744,15740,15748,15741,15759,15755,15758,15738,15747,15754,15761,15746,15745,15735,15724,15737,15739,15762,15751,15760,15753,15734,15756,15743],"class_list":["post-2805","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hosting-news","tag-audit-servicii-vps-linux-hardening","tag-blocare-cups-firewalld-rocky-linux","tag-blocare-port-cups-631-ufw-firewall","tag-cum-verifici-daca-cups-ruleaza-linux","tag-cups-2-4-17-update-securitate","tag-cups-cups-browsed-expus-retea-server","tag-cve-2026-34980-injectare-newline-page-border-parsare","tag-cve-2026-34980-openprinting-cups-remediere","tag-cve-2026-34990-abuz-token-ipp-localhost","tag-cve-2026-34990-escaladare-privilegii-cups-root","tag-dezactivare-cups-alpine-linux-openrc","tag-dezactivare-cups-freebsd-rc-conf","tag-dezactivare-cups-ubuntu-debian-rocky-almalinux","tag-dezactivare-cups-vps-linux-securitate","tag-dezactivare-cups-browsed-server-linux","tag-exploatare-activa-cups-confirmata-2026","tag-exploit-coada-postscript-cups","tag-exploit-job-imprimare-cups-neautentificat","tag-lant-cups-rce-lp-la-root","tag-lant-exploit-cups-rce-neautentificat-executie-cod-de-la-distanta","tag-openprinting-cups-scheduler-rce-2026","tag-oprire-dezactivare-mascare-cups-systemctl","tag-portul-631-cups-expus-vps","tag-serverspan-vps-securitate-hardening-linux","tag-suprafata-de-atac-cups-server-vps","tag-suprascriere-arbitrara-fisier-cups-root-sudoers","tag-systemctl-mask-cups-hardening-securitate","tag-vulnerabilitate-cups-aprilie-2026-patch","tag-vulnerabilitate-cups-imagine-os-de-baza-vps","tag-vulnerabilitate-cups-rce-cve-2026-34980-server-linux-remediere"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2805","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2805"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2805\/revisions"}],"predecessor-version":[{"id":2806,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2805\/revisions\/2806"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2803"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2805"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2805"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2805"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}