{"id":2146,"date":"2025-12-19T17:48:12","date_gmt":"2025-12-19T17:48:12","guid":{"rendered":"https:\/\/blog.eu.enginyr.ing\/?p=2146"},"modified":"2025-12-19T17:48:27","modified_gmt":"2025-12-19T17:48:27","slug":"cve-2025-11234-vulnerabilitatea-qemu-kvm-vnc-websocket-use-after-free-permite-dos-inainte-de-autentificare","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/cve-2025-11234-vulnerabilitatea-qemu-kvm-vnc-websocket-use-after-free-permite-dos-inainte-de-autentificare\/","title":{"rendered":"CVE-2025-11234: Vulnerabilitatea QEMU-KVM VNC WebSocket use-after-free permite DoS \u00eenainte de autentificare"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">\u00cen peisajul securit\u0103\u021bii virtualiz\u0103rii, pu\u021bine lucruri \u021bin administratorii de sistem treji noaptea la fel ca o vulnerabilitate pre-autentificare \u00een stiva hypervisorului. CVE-2025-11234 este exact acel scenariu de co\u0219mar. Este o vulnerabilitate critic\u0103 de tip use-after-free (UAF) descoperit\u0103 \u00een implementarea QEMU VNC WebSocket, care pune \u00een pericol imediat infrastructura de virtualizare\u2014de la mici cloud-uri private p\u00e2n\u0103 la platforme multi-tenant masive. Aceast\u0103 vulnerabilitate permite atacatorilor cu acces simplu la re\u021bea c\u0103tre portul VNC s\u0103 declan\u0219eze un denial of service (DoS) \u00een timpul fazei de handshake, pr\u0103bu\u0219ind efectiv procesul QEMU \u00eenainte ca orice date de autentificare s\u0103 fie schimbate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Defec\u021biunea afecteaz\u0103 gestionarea obiectului <code>QIOChannelWebsock<\/code> \u00een <code>qemu-kvm<\/code> pe mai multe distribu\u021bii Linux, inclusiv Red Hat Enterprise Linux (RHEL), CentOS, Debian \u0219i Ubuntu. Red Hat a evaluat aceast\u0103 severitate ca fiind moderat\u0103 spre ridicat\u0103, lans\u00e2nd avizul de securitate RHSA-2025:23228. Pentru orice echip\u0103 care gestioneaz\u0103 infrastructur\u0103 virtualizat\u0103, \u00een\u021belegerea mecanicii acestui bug nu este un exerci\u021biu academic\u2014este o necesitate opera\u021bional\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La <a href=\"https:\/\/www.enginyring.com\/ro\/virtual-servers\">ENGINYRING<\/a>, am petrecut ultima s\u0103pt\u0103m\u00e2n\u0103 audit\u00e2nd clustere \u0219i aplic\u00e2nd patch-uri hypervizoarelor \u00eempotriva acestei amenin\u021b\u0103ri specifice. Din experien\u021ba noastr\u0103, vulnerabilit\u0103\u021bile de acest gen sunt \u00een\u0219el\u0103toare; par a fi simple erori care duc la blocarea sistemului (&#8220;crash bugs&#8221;), dar mecanismele de corupere a memoriei care stau la baz\u0103 ascund adesea poten\u021bialul pentru execu\u021bie de cod la distan\u021b\u0103 (RCE). Dac\u0103 porturile tale VNC sunt expuse la internet sau accesibile din VLAN-uri interne nesigure, infrastructura ta func\u021bioneaz\u0103 \u00een prezent pe timp \u00eemprumutat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Anatomia unui use-after-free \u00een virtualizare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a \u00een\u021belege de ce CVE-2025-11234 este periculos, trebuie s\u0103 privim &#8220;sub capota&#8221; gestion\u0103rii evenimentelor \u00een QEMU. QEMU este o aplica\u021bie orientat\u0103 pe evenimente. Se bazeaz\u0103 foarte mult pe mecanismul Main Loop \u0219i <code>GSource<\/code> din GLib pentru a gestiona evenimente asincrone, cum ar fi I\/O de re\u021bea, timere \u0219i \u00eentreruperi hardware. C\u00e2nd te conectezi la consola VNC a unei ma\u0219ini virtuale (VM) printr-un WebSocket, QEMU nu doar blocheaz\u0103 \u0219i te a\u0219teapt\u0103; \u00eenregistreaz\u0103 o &#8220;surs\u0103&#8221; (o func\u021bie callback) \u00een bucla principal\u0103 de evenimente pentru a asculta date pe acel socket.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Condi\u021bia de curs\u0103 GSource<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Vulnerabilitatea specific\u0103 rezid\u0103 \u00een modul \u00een care QEMU gestioneaz\u0103 ciclul de via\u021b\u0103 al obiectului <code>QIOChannelWebsock<\/code>. Acest obiect reprezint\u0103 starea conexiunii WebSocket. \u00centr-un flux de lucru normal, un client se conecteaz\u0103, are loc handshake-ul, iar canalul devine activ. Totu\u0219i, programarea de re\u021bea este rareori &#8220;normal\u0103&#8221;. Conexiunile cad, apar timeout-uri, iar pachetele sosesc \u00een dezordine.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Eroarea apare atunci c\u00e2nd obiectul <code>QIOChannelWebsock<\/code> este eliberat din memorie\u2014poate din cauza unei erori de conexiune sau a unui timeout\u2014\u00een timp ce tehnic \u00eenc\u0103 &#8220;a\u0219teapt\u0103&#8221; finalizarea handshake-ului. Crucial este faptul c\u0103 codul nu reu\u0219e\u0219te s\u0103 dez\u00eenregistreze corect <code>GSource<\/code>-ul asociat din bucla principal\u0103 de evenimente \u00eenainte de a elibera memoria.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Iat\u0103 secven\u021ba e\u0219ecului:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Ini\u021biere conexiune:<\/strong> Un client ini\u021biaz\u0103 o conexiune VNC WebSocket. QEMU aloc\u0103 un obiect <code>QIOChannelWebsock<\/code>.<\/li>\n<li><strong>\u00cenregistrare surs\u0103:<\/strong> QEMU ata\u0219eaz\u0103 un <code>GSource<\/code> la bucla de evenimente pentru a monitoriza finalizarea handshake-ului WebSocket.<\/li>\n<li><strong>Cur\u0103\u021bare prematur\u0103:<\/strong> Atacatorul declan\u0219eaz\u0103 o condi\u021bie (cum ar fi o deconectare rapid\u0103 sau un cadru malformat) care determin\u0103 QEMU s\u0103 elibereze obiectul <code>QIOChannelWebsock<\/code>.<\/li>\n<li><strong>Referin\u021ba suspendat\u0103:<\/strong> <code>GSource<\/code>-ul r\u0103m\u00e2ne activ \u00een bucla de evenimente, indic\u00e2nd spre adresa de memorie unde se afla obiectul <em>anterior<\/em>.<\/li>\n<li><strong>Pr\u0103bu\u0219irea (Crash):<\/strong> Bucla de evenimente declan\u0219eaz\u0103 callback-ul. Callback-ul \u00eencearc\u0103 s\u0103 citeasc\u0103 de la adresa de memorie eliberat\u0103 (Use-After-Free). Procesul se pr\u0103bu\u0219e\u0219te imediat din cauza unei erori de segmentare sau a coruperii memoriei.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">\u00centr-un mediu administrat precum serviciul nostru de <a href=\"https:\/\/www.enginyring.com\/ro\/proxmox-management\">management Proxmox<\/a>, monitoriz\u0103m aceste erori de segmentare specifice \u00een jurnalele hypervisorului, deoarece sunt adesea primul indicator al unei scan\u0103ri sau al unui atac.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De ce \u201epre-autentificarea\u201d schimb\u0103 modelul de amenin\u021bare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cel mai critic aspect al CVE-2025-11234 este sintagma &#8220;pre-autentificare&#8221;. \u00cen ierarhia vulnerabilit\u0103\u021bilor, acestea sunt cele mai severe, deoarece elimin\u0103 bariera de intrare. Un atacator nu are nevoie s\u0103 compromit\u0103 un cont de utilizator, s\u0103 fure o cheie SSH sau s\u0103 ghiceasc\u0103 o parol\u0103 VNC. Are nevoie doar de conectivitate TCP c\u0103tre portul \u021bint\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru extinde semnificativ suprafa\u021ba de atac \u00een trei scenarii distincte:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Expunerea consolei \u00een cloud public<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Mul\u021bi furnizori de hosting \u0219i configura\u021bii de cloud privat ofer\u0103 clien\u021bilor acces la &#8220;Consola VNC&#8221;. Adesea, aceasta este trecut\u0103 printr-un proxy, dar \u00een unele configura\u021bii vechi sau gre\u0219ite, portul VNC WebSocket (care \u00eencepe de la 5700) este expus direct la internet pentru a permite clien\u021bilor noVNC s\u0103 se conecteze. Dac\u0103 infrastructura ta se potrive\u0219te acestei descrieri, fiecare VM este o \u021bint\u0103. Un atacator poate scana porturile deschise 5700-5799 \u0219i poate pr\u0103bu\u0219i sistematic procesele QEMU, cauz\u00e2nd o \u00eentrerupere masiv\u0103 a instan\u021belor clien\u021bilor.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Re\u021beaua intern\u0103 \u201esigur\u0103\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Vedem adesea re\u021bele interne tratate ca &#8220;zone sigure&#8221; unde regulile de firewall sunt relaxate. &#8220;Este \u00een spatele VPN-ului, deci e \u00een regul\u0103&#8221;, este un sentiment comun. Totu\u0219i, dac\u0103 un actor r\u0103u inten\u021bionat c\u00e2\u0219tig\u0103 un punct de sprijin pe o singur\u0103 sta\u021bie de lucru sau \u00eentr-un container compromis din acea re\u021bea, poate folosi CVE-2025-11234 pentru a dobor\u00ee host-uri critice de virtualizare. Atacatorii interni sunt deosebit de periculo\u0219i, deoarece adesea au mapat\u0103 infrastructura \u0219i \u0219tiu exact care host-uri ruleaz\u0103 baze de date critice.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Hosting partajat \u0219i multi-tenancy<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen mediile multi-tenant, un chiria\u0219 r\u0103u inten\u021bionat ar putea perturba vecinii. Dac\u0103 segmentarea re\u021belei \u00eentre VM-urile invitate \u0219i interfa\u021ba de administrare a hypervisorului nu este strict aplicat\u0103 (o problem\u0103 comun\u0103 \u00een design-urile de re\u021bea &#8220;plate&#8221;), o ma\u0219in\u0103 virtual\u0103 compromis\u0103 ar putea ataca porturile VNC ale VM-urilor adiacente de pe acela\u0219i host sau cluster.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Evaluarea impactului: denial of service \u0219i mai mult<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">De\u0219i impactul primar \u0219i cel mai imediat este Denial of Service (DoS), administratorii de sistem nu ar trebui s\u0103 fie complezen\u021bi. O pr\u0103bu\u0219ire a QEMU este disruptiv\u0103\u2014for\u021beaz\u0103 o repornire hardware a VM-ului, corup\u00e2nd poten\u021bial bazele de date sau sistemele de fi\u0219iere care nu au fost scrise corect pe disc. Pentru un cluster de \u00eenalt\u0103 disponibilitate (HA), o pr\u0103bu\u0219ire simultan\u0103 a mai multor procese QEMU poate destabiliza \u00eentregul nod, declan\u0219\u00e2nd agen\u021bi de fencing \u0219i bucle de failover haotice.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Totu\u0219i, \u00eengrijorarea pe termen lung cu bug-urile Use-After-Free este \u00eentotdeauna <strong>Execu\u021bia de cod la distan\u021b\u0103 (RCE)<\/strong>. De\u0219i dificil, este teoretic posibil ca un atacator sofisticat s\u0103 manipuleze memoria heap (Heap Feng Shui) astfel \u00eenc\u00e2t regiunea de memorie eliberat\u0103 s\u0103 fie realocat\u0103 unui nou obiect controlat de atacator. C\u00e2nd callback-ul <code>GSource<\/code> suspendat se execut\u0103, acesta ar putea citi date din acest obiect &#8220;fals&#8221;, redirec\u021bion\u00e2nd poten\u021bial fluxul de execu\u021bie al codului.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Istoric, evadarea din ma\u0219ina virtual\u0103 (VM Escape) este \u201eSf\u00e2ntul Graal\u201d al exploat\u0103rii hypervizoarelor. De\u0219i CVE-2025-11234 provine din partea de re\u021bea (interfa\u021ba de management) mai degrab\u0103 dec\u00e2t din interiorul guest-ului, un exploit RCE aici ar acorda atacatorului privilegii de execu\u021bie ale procesului QEMU pe sistemul gazd\u0103. \u00cen func\u021bie de <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/cum-sa-securizezi-un-vps-proaspat-un-ghid-cuprinzator-pentru-incepatori-in-linux\">configura\u021bia de securitate a VPS-ului<\/a>, acesta ar putea rula ca root sau ca un utilizator dedicat <code>qemu<\/code> cu capacit\u0103\u021bi semnificative (cum ar fi accesarea dispozitivelor bloc sau a interfe\u021belor de re\u021bea).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identificarea sistemelor vulnerabile<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a putea remedia problema, trebuie s\u0103 o cuantifici. Vulnerabilitatea exist\u0103 \u00een codul surs\u0103 QEMU upstream, ceea ce \u00eenseamn\u0103 c\u0103 afecteaz\u0103 practic orice distribu\u021bie care nu a aplicat patch-ul specific (backport) pentru <code>io\/channel-websock.c<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Verificarea versiunii<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Trebuie s\u0103 auditezi host-urile hypervisor, nu VM-urile invitate. Ruleaz\u0103 urm\u0103toarele comenzi pentru a verifica versiunile instalate:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Red Hat \/ CentOS \/ AlmaLinux:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rpm -qa | grep qemu-kvm<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caut\u0103 versiuni anterioare lui <code>qemu-kvm-8.2.0-11.el9_4.18<\/code> pe sistemele RHEL 9. Distribu\u021biile mai vechi (CentOS 7\/8) vor avea \u0219iruri de versiuni diferite, dar necesit\u0103 patch-uri echivalente.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Debian \/ Ubuntu:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg -l | grep qemu-system<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Debian, verific\u0103 trackerul de securitate pentru versiunea ta specific\u0103 (Bullseye, Bookworm, Trixie). Versiunile Ubuntu LTS (20.04, 22.04, 24.04) lanseaz\u0103 de obicei aceste actualiz\u0103ri prin canalul <code>-security<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Auditarea ascult\u0103torilor activi<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Doar faptul c\u0103 ai pachetul instalat nu \u00eenseamn\u0103 c\u0103 e\u0219ti expus. E\u0219ti vulnerabil doar dac\u0103 VNC WebSockets sunt active. Folose\u0219te <code>ss<\/code> (Socket Statistics) pentru a g\u0103si procesele care ascult\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ss -lntp | grep qemu<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Traficul VNC standard ascult\u0103 de obicei pe 5900+ (TCP). Traficul <strong>WebSocket<\/strong> ascult\u0103 de obicei pe 5700+ (TCP). Dac\u0103 vezi linii precum <code>0.0.0.0:5700<\/code>, host-ul t\u0103u ascult\u0103 pe toate interfe\u021bele \u0219i e\u0219ti expus critic. Dac\u0103 vezi <code>127.0.0.1:5700<\/code>, ascul\u021bi doar local (mai sigur, dar totu\u0219i vulnerabil la atacatori locali sau ocolirea proxy-ului).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Strategii de remediere \u0219i atenuare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Remedierea vulnerabilit\u0103\u021bilor hypervisorului este grea din punct de vedere opera\u021bional. Spre deosebire de actualizarea unei aplica\u021bii web, nu po\u021bi pur \u0219i simplu s\u0103 dai &#8220;reload&#8221; la QEMU f\u0103r\u0103 a opri VM-ul pe care \u00eel sus\u021bine. Remedierea necesit\u0103 o strategie care echilibreaz\u0103 urgen\u021ba securit\u0103\u021bii cu cerin\u021bele de uptime. Recomand\u0103m urm\u0103toarea abordare stratificat\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Strategia A: Patch-ul complet (Recomandat)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Singura modalitate de a elimina bug-ul este \u00eenlocuirea binarului. Acest lucru necesit\u0103 repornirea fiec\u0103rui proces QEMU.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Actualizeaz\u0103 Host-ul:<\/strong> Ruleaz\u0103 <code>yum update qemu-kvm<\/code> sau <code>apt install --only-upgrade qemu-system-x86<\/code>. Verific\u0103 dac\u0103 noua versiune este instalat\u0103.<\/li>\n<li><strong>Gole\u0219te Nodul (Migrare Live):<\/strong> Dac\u0103 rulezi un cluster (precum Proxmox sau OpenStack), migreaz\u0103 live VM-urile care ruleaz\u0103 pe un host deja actualizat. Acest lucru p\u0103streaz\u0103 uptime-ul pentru fluxurile de lucru.<\/li>\n<li><strong>Reboot\/Restart:<\/strong> Dac\u0103 nu po\u021bi migra, trebuie s\u0103 opre\u0219ti VM-urile \u0219i s\u0103 le porne\u0219ti din nou. Un simplu reboot \u00een sistemul de operare guest <strong>nu este suficient<\/strong>; asta reporne\u0219te doar kernel-ul guest, nu procesul QEMU de pe host. Trebuie s\u0103 opre\u0219ti complet \u0219i s\u0103 porne\u0219ti instan\u021ba VM.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru detalii despre gestionarea \u00een siguran\u021b\u0103 a actualiz\u0103rilor, consult\u0103 ghidul nostru despre <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/update-vs-upgrade-de-server-care-este-diferenta-si-de-ce-este-importanta\">diferen\u021ba dintre update \u0219i upgrade de server<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Strategia B: Dezactivarea suportului WebSocket (Configurare)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu po\u021bi aplica patch-ul imediat, po\u021bi atenua vulnerabilitatea dezactiv\u00e2nd func\u021bionalitatea WebSocket. Majoritatea mediilor folosesc VNC standard (port 59xx) pentru administrare \u0219i activeaz\u0103 WebSockets (port 57xx) doar pentru clien\u021bi baza\u021bi pe browser, precum noVNC.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen <code>\/etc\/libvirt\/qemu.conf<\/code>, caut\u0103 configura\u021bia VNC. Asigur\u0103-te c\u0103 ascult\u0103torii WebSocket sunt dezactiva\u021bi sau nu sunt defini\u021bi. Dac\u0103 folose\u0219ti linii de comand\u0103 QEMU direct, elimin\u0103 parametrul <code>websocket=on<\/code> din argumentul <code>-vnc<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Strategia C: Segmentarea re\u021belei (Firewall)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 trebuie neap\u0103rat s\u0103 p\u0103strezi WebSockets func\u021bionale pentru o anumit\u0103 aplica\u021bie, trebuie s\u0103 izolezi traficul. Nu permite \u00eentregului internet s\u0103 ajung\u0103 la portul 5700. Folose\u0219te <code>nftables<\/code> sau <code>iptables<\/code> pentru a permite accesul (whitelist) doar bastionului t\u0103u de management sau gateway-ului VPN.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Exemplu regul\u0103 nftables pentru a permite VNC WebSockets doar de la 10.10.50.5 (Bastion)\nadd rule ip filter input tcp dport 5700-5799 saddr 10.10.50.5 accept\nadd rule ip filter input tcp dport 5700-5799 drop<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru nu repar\u0103 bug-ul\u2014codul este \u00eenc\u0103 vulnerabil\u2014dar reduce drastic suprafa\u021ba de atac doar la ma\u0219inile de \u00eencredere.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Strategia D: \u00cencapsularea prin Reverse Proxy (Abordarea profesionist\u0103)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen infrastructura noastr\u0103 administrat\u0103, rareori expunem porturile QEMU direct. \u00cen schimb, recomand\u0103m plasarea unui reverse proxy precum Nginx sau HAProxy \u00een fa\u021ba VNC WebSocket. Acest lucru ofer\u0103 dou\u0103 beneficii masive: rupe conexiunea TCP direct\u0103 (poten\u021bial protej\u00e2nd QEMU de pachete malformate) \u0219i adaug\u0103 un strat de autentificare (SSL\/TLS + Basic Auth) <em>\u00eenainte<\/em> ca traficul s\u0103 ajung\u0103 vreodat\u0103 la QEMU.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Iat\u0103 o configura\u021bie Nginx robust\u0103 pentru a proteja un VNC WebSocket vulnerabil:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>server {\n    listen 443 ssl;\n    server_name vnc.domeniultau.com;\n\n    # Certificate SSL\n    ssl_certificate \/etc\/nginx\/ssl\/fullchain.pem;\n    ssl_certificate_key \/etc\/nginx\/ssl\/privkey.pem;\n\n    location \/websockify {\n        # Proxy c\u0103tre QEMU WebSocket local (leag\u0103 QEMU doar pe 127.0.0.1!)\n        proxy_pass http:\/\/127.0.0.1:5700;\n        \n        # Suport WebSocket\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection \"upgrade\";\n        \n        # Securitate: Permite doar utilizatori autentifica\u021bi\n        auth_basic \"Acces VNC Restric\u021bionat\";\n        auth_basic_user_file \/etc\/nginx\/.htpasswd;\n    }\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Folosind aceast\u0103 metod\u0103, un atacator care \u00eencearc\u0103 s\u0103 exploateze CVE-2025-11234 ar trebui mai \u00eent\u00e2i s\u0103 treac\u0103 de autentificarea Nginx. Deoarece exploit-ul este pre-autentificare la nivelul VNC, ad\u0103ugarea HTTP Basic Auth neutralizeaz\u0103 eficient aspectul &#8220;neautentificat&#8221; al amenin\u021b\u0103rii.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Detectarea exploat\u0103rii active<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cum \u0219tii dac\u0103 cineva \u00eencearc\u0103 deja s\u0103-\u021bi pr\u0103bu\u0219easc\u0103 serverele? Trebuie s\u0103 te ui\u021bi \u00een jurnale. Un atac DoS reu\u0219it prin aceast\u0103 vulnerabilitate va rezulta \u00een terminarea nea\u0219teptat\u0103 a procesului QEMU.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 jurnalul de sistem pentru erori de segmentare (segmentation faults) legate de <code>qemu-kvm<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>journalctl -xe | grep \"segfault\" | grep \"qemu\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">S-ar putea s\u0103 vezi intr\u0103ri similare cu:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>kernel: qemu-kvm[12345]: segfault at 0000000000000010 ip 00007f&#8230; sp 00007f&#8230; error 4 in qemu-kvm<\/p><\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen plus, verific\u0103 jurnalele libvirt situate \u00een <code>\/var\/log\/libvirt\/qemu\/<\/code>. Dac\u0103 vezi ini\u021bializ\u0103ri repetate de conexiuni urmate imediat de &#8220;connection closed&#8221; sau terminarea procesului f\u0103r\u0103 un semnal de oprire curat, investigheaz\u0103 imediat adresele IP surs\u0103 ale acelor conexiuni. Pentru un ghid mai larg despre monitorizarea securit\u0103\u021bii, consult\u0103 articolul nostru despre <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/cum-sa-detectezi-intrusi-in-serverul-tau-vps-ghid-complet-de-securitate\">detectarea intru\u0219ilor \u00een VPS-ul t\u0103u<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Costul opera\u021bional al virtualiz\u0103rii neadministrate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Vulnerabilit\u0103\u021bi precum CVE-2025-11234 eviden\u021biaz\u0103 costurile ascunse ale gestion\u0103rii propriei stive de virtualizare. Nu este vorba doar despre pornirea VM-urilor; este vorba despre urm\u0103rirea CVE-urilor upstream, \u00een\u021belegerea nuan\u021bei dintre un rating &#8220;moderat&#8221; \u0219i unul &#8220;critic&#8221; \u0219i a avea \u00eencrederea inginereasc\u0103 de a efectua migr\u0103ri live sau fluxuri complexe de patch-uri la 3 diminea\u021ba.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru afacerile care au nevoie de puterea KVM f\u0103r\u0103 durerea de cap a administr\u0103rii de sistem, oferim solu\u021bii complet administrate. Fie c\u0103 ai nevoie de <a href=\"https:\/\/www.enginyring.com\/ro\/virtual-servers\">Servere Virtuale<\/a> izolate sau de un contract dedicat de <a href=\"https:\/\/www.enginyring.com\/ro\/proxmox-management\">Management Proxmox<\/a>, ENGINYRING se asigur\u0103 c\u0103 hypervisorul de baz\u0103 este actualizat, \u00eent\u0103rit \u0219i monitorizat. Ne ocup\u0103m noi de scurgerile <code>GSource<\/code> \u0219i bug-urile de corupere a memoriei, astfel \u00eenc\u00e2t tu s\u0103 te po\u021bi concentra pe aplica\u021biile tale.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mai mult, a avea o strategie robust\u0103 de backup este plasa de siguran\u021b\u0103 final\u0103 \u00eempotriva oric\u0103rui eveniment DoS sau de corup\u021bie. Asigur\u0103-te c\u0103 urmezi <a href=\"https:\/\/www.enginyring.com\/ro\/blog\/strategii-automate-de-backup-pentru-vps-rsync-restic-si-stocare-off-site\">cele mai bune practici pentru backup automat<\/a> pentru a garanta c\u0103, chiar dac\u0103 un hypervisor se pr\u0103bu\u0219e\u0219te, datele tale r\u0103m\u00e2n sigure \u0219i recuperabile.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Rezumatul ac\u021biunilor necesare<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Audit:<\/strong> Identific\u0103 toate sistemele care ruleaz\u0103 <code>qemu-kvm<\/code> \u0219i verific\u0103 porturile care ascult\u0103 pe 57xx.<\/li>\n<li><strong>Patch:<\/strong> Programeaz\u0103 ferestre de mentenan\u021b\u0103 pentru a actualiza QEMU la versiunea 8.2.0-11.el9_4.18 (RHEL) sau echivalent\u0103.<\/li>\n<li><strong>Reboot:<\/strong> Re\u021bine c\u0103 actualizarea pachetului nu este suficient\u0103; procesul trebuie s\u0103 reporneasc\u0103.<\/li>\n<li><strong>Izolare:<\/strong> Dac\u0103 aplicarea patch-ului este \u00eent\u00e2rziat\u0103, pune firewall pe porturile VNC sau trece-le printr-un reverse proxy Nginx cu autentificare.<\/li>\n<li><strong>Monitorizare:<\/strong> Configureaz\u0103 alerte pentru erori de segmentare QEMU \u00een sistemul t\u0103u centralizat de logare.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>\u00cen peisajul securit\u0103\u021bii virtualiz\u0103rii, pu\u021bine lucruri \u021bin administratorii de sistem treji noaptea la fel ca o vulnerabilitate pre-autentificare \u00een stiva hypervisorului. CVE-2025-11234 este exact acel scenariu de co\u0219mar. Este o vulnerabilitate critic\u0103 de tip use-after-free (UAF) descoperit\u0103 \u00een implementarea QEMU VNC WebSocket, care pune \u00een pericol imediat infrastructura de virtualizare\u2014de la mici cloud-uri private p\u00e2n\u0103 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2144,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[13093,13087,13086,13088,13095,13061,13082,13094,13081,13096,13089,13092,13083,13091,13060,13067,13084,13090,13085,13080],"class_list":["post-2146","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-virtual-servers","tag-actualizari-securitate-enterprise-linux","tag-analiza-crash-qemu-kvm","tag-bug-bucla-evenimente-gsource","tag-configurare-vnc-sigura","tag-corupere-memorie-qemu","tag-cve-2025-11234","tag-denial-of-service-pre-autentificare","tag-detectare-cve-2025-11234","tag-exploit-qiochannelwebsock","tag-ghid-securitate-sysadmin","tag-intarire-securitate-libvirt","tag-migrare-live-virtualizare","tag-patch-securitate-hypervisor","tag-proxy-nginx-vnc","tag-qemu-kvm-use-after-free","tag-rhsa-202523228","tag-securitate-infrastructura-virtualizare","tag-securitate-virtualizare-linux","tag-strategii-atenuare-kvm","tag-vulnerabilitate-vnc-websocket"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2146","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=2146"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2146\/revisions"}],"predecessor-version":[{"id":2147,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2146\/revisions\/2147"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2144"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}