Télécharger Logiciels > Système > Virtualisation > Sandboxie 5.74.0 fr

Sandboxie 5.74.0 fr

Sandboxie permet de protéger votre ordinateur d'éventuels malwares, virus, chevaux de Troie… en installant une ''sandbox'' (bac à sable *) qui va se glisser entre vos applications et votre disque dur. Cela permet d'isoler le fonctionnement des applications du système d'exploitation en créant ainsi un environnement sécurisé.

Ainsi, les modifications effectuées sous la protection de Sandboxie ne sont pas effectives dans les fichiers authentiques. Les parasites et les bogues qui y sont enfermés n'affectent pas le système d'exploitation. Toutes les traces laissées par vos activités Online (favoris, cookies, historique, cache Internet…) seront également sous le contrôle de Sandboxie. De plus, Sandboxie interdit depuis la zone qu'il contrôle toute injection dans le noyau de Windows (driver, DLL…).

Les nouveautés ou un changement qui doit être conservé devront être enregistrés hors du sandbox après avoir vérifié leur validité.

L'interface de contrôle permet d'afficher la liste des processus activés dans l'environnement et de les gérer, ou de gérer le contenu d'une ''sandbox'', le logiciel vous permettant d'en créer d'autres.

Il suffira de vider le contenu du bac à sable avant de terminer une cession d'utilisation de l'ordinateur pour que toutes les traces inutiles ou dangereuses isolées dans le bac à sable soient définitivement effacées du disque… Virus, chevaux de Troie, logiciels espions, et autres logiciels malveillants, ainsi que l’historique et le contenu du cache de navigation.

Au bout de 30 jours, le programme lancera occasionnellement un message vous demandant si vous voulez acheter une licence, mais dans tous les cas les fonctions demeurent.

* Par ''sandbox'' (littéralement ''bac à sable'') on entend un procédé d'isolation destiné au fonctionnement d'un logiciel dans un espace séparé et confiné de l'ordinateur. À l'origine, la technique ''sandbox'' était utilisée essentiellement pour sécuriser les applets Java. Elle peut servir de cadre virtuel pour éviter la corruption du système en cas de problème : bogue d'une application, attaque de malwares, …


Compléments

Nouveautés & Corrections
Version 5.74.0 du 28/10/2026
- Fixed kernel pool out-of-bounds write in Api_CopyStringFromUser, which placed the terminator one character past its allocation and copied two bytes beyond the caller's string (reached through API_UPDATE_CONF)
- Fixed Session_ListLock and the raised IRQL being leaked for the lifetime of the driver when the monitor put handlers faulted on a user mode string
- Fixed API_MONITOR_GET_EX copying eight bytes of the log buffer past each entry, and its bounds check being defeated by a USHORT cast and a signed underflow
- Fixed kernel stack buffer overflow in _wntoi when a box's NetworkAccess rule carried a long port token
- Fixed BlockLocalLoop never blocking IPv4 loopback, because WFP_isLoopback tested the last octet of the address instead of the first
- Fixed kernel pool over-read in the rename/link minifilter path, where FileNameLength out of the caller's information buffer was used as a length without being checked against that buffer
- Fixed the new LPC implementation leaking the per-connection port handle and any pending reassembly buffer on every disconnect
- Fixed concurrent requests on one LPC connection racing the shared reassembly state, which could free it twice
- Fixed stack buffer overflow in MSGID_SBIE_INI_SET_DAT, where the unterminated setting field was appended to a - Fixed size path buffer
- Fixed SbieIniServer abandoning its critical section when a handler faulted, which left every later INI request blocked on it
- Fixed value_len being truncated while scaled to bytes in the INI setting and template handlers, so a large value passed the bounds check and was then read far past the message
- Fixed GUI_MAP_WINDOW_POINTS copying more points out of a request than it actually carried, returning service heap to the caller
- Fixed WndHookRegisterSlave returning while holding m_SlavesLock on two caller reachable rejections, which wedged the GUI proxy for the rest of the session
- Fixed GUI_GET_RAW_INPUT_DEVICE_INFO truncating its size while scaling it to bytes, so an over large cbSize skipped both bounds checks and was handed to the OS as a buffer size
- Fixed the desktop startExplorer and startRun actions launching as LocalSystem rather than with the calling user's token
- Fixed PORT_DATA_INFO being read without requiring the whole structure to lie inside the LPC message
- Fixed the ALPC connect reply returning its uninitialised tail - up to PIPE_MAX_DATA_LEN of service heap - to the caller
- Fixed global ("asterisk") queue names having no session scoping, which let any unsandboxed process squat a well-known name such as the interactive queue
- Fixed the UAC packet being accepted with no minimum length, and its string offsets being used without being checked against it
- Fixed the ICMP echo reply fix-up writing a whole ICMP_ECHO_REPLY past a caller sized reply buffer when the echo itself failed
- Fixed request_size not being checked against the message in the ICMP echo handler, which put up to 64 KB of service heap on the wire
- Fixed m_WorkersList being mutated without taking the lock that exists for it, so concurrent startup requests could close and free the same worker twice
- Fixed UserServer::OpenFile using unvalidated request offsets, and matching the box's file rules against a path that was not canonical
- Fixed a WCHAR/byte length confusion in the SbieDrv API_GET_FILE_NAME handler that over-read the file-object name into the caller's buffer
- Fixed two paged-pool leaks in the SbieDrv API_RENAME_FILE handler (an early return and a faulting user copy) reachable by a sandboxed process
- Fixed the SbieDrv API_OPEN_FILE handler not checking its allocation and leaking it when the user copy faulted
- Fixed the spooler ALPC message filter being dead code on Windows 8.1+ (the driver compared the port id against the wrong literal, so the filter never armed)
- Fixed a kernel NULL-pointer dereference and a NonPagedPool leak in the NetworkAccess firewall-rule parser (netfw.c)
- Fixed a wrong range-overlap test in the firewall-rule parser that could insert overlapping ranges and make a Block rule stop matching
- Fixed two paged-pool leaks on the error paths of the driver configuration variable expander (Conf_Expand_2)
- Fixed the SbieDrv API_IS_BOX_ENABLED handler dereferencing an unprobed user SID pointer in kernel mode
- Fixed proc->file_lock and the raised IRQL being leaked if WFP_UpdateProcess faulted in the SbieDrv API_REFRESH_FILE_PATH_LIST handler
- Fixed a use-after-free of a protected-root list entry in the file minifilter (the node was read after its lock was released)
- Fixed proc->threads_lock being leaked if the output write faulted in the itok/ttok paths of the SbieDrv process-query handler
- Fixed the duplicated-handle access re-validation being skipped for Directory/SymbolicLink/Job objects in Syscall_DuplicateHandle_3 (a loop counter clobbered the type length before the suffix test)
- Fixed the SbieDrv API_OPEN_PROCESS handler dereferencing the terminated-process sentinel with a lock held when asked for PID 0
- Fixed two token references and a handle being leaked if the output write faulted in the SbieDrv API_FILTER_TOKEN handler
- Fixed a 32-bit truncation of the entry size in the driver monitor-log writer that could overflow the log buffer
- Fixed SandMan over-reading an unterminated file path out of a queue reply (MAN_FILE_MIGRATION), which a sandboxed process could use to crash the UI
- Fixed INI section names not being rejected for CR/LF or brackets, which let a caller forge additional sections/settings and bypass a per-section EditAdminOnly lock
- Fixed the SbieSvc USER_SHELL_EXEC handler using an unvalidated, possibly-unterminated wire path offset
- Fixed the SbieSvc MSGID_SBIE_INI_SET_DAT handler using an unvalidated value_len as the write length, reading past the request buffer
- Fixed the INI setting handlers not terminating their - Fixed-size section/setting/password wire fields before use
- Fixed a per-message heap leak in the SbieSvc log drain loop (DriverAssist::LogMessage)
- Fixed GUI_CHANGE_DISPLAY_SETTINGS passing an unterminated device name and an unbounded DEVMODE to the display API
- Fixed GUI_GRANT_HANDLE leaking the two bitmaps GetIconInfo creates on every call
- Fixed GUI_GET_WINDOW_PROP and GUI_FIND_WINDOW treating a caller-chosen value outside the atom range as a raw string pointer
- Fixed GUI_SET_CLIPBOARD_DATA not validating the request length and not bounding the caller-supplied data length
- Fixed the SbieSvc process-info handler disclosing any process's command line/image path to any local user (now restricted to the caller's session or administrators)
- Fixed the SbieSvc WOW64 registry-open handler indexing a - Fixed prefix of KeyPath without checking its length or termination
- Fixed the SbieSvc named-pipe read handler returning the uninitialised tail of its reply buffer (information disclosure)
- Fixed the SbieSvc terminal GetName handler leaking uninitialised stack into its reply and terminating the wrong buffer
- Fixed the four SbieSvc terminal query handlers having no caller gate and taking a session id off the wire, letting any user query other sessions as SYSTEM; QUERY_INFO now also allow-lists the information class
- Fixed the SbieSvc ImBox QueryHandler leaking its critical section (and deadlocking the mount subsystem) when the queried mount raced to NULL
- Fixed the SbieSvc queue server accepting an unbounded number of undrained requests (per-queue cap added)


Mis à jour le : 28.10.26

Capture d'ecran du logiciel Sandboxie 5.74.0 fr


Informations & Téléchargements
 Système :
Windows 7/8/8.1/10/11
 Version :
5.74.0 - 64bit
 Licence :
Open-Source
 Limitation :
Aucune
 Taille du Fichier :
3 MB
 Langue :
Anglais / Français
 Téléchargé(s) :
1988 fois
 Editeur :
 Prix :
Gratuit
 Note : 
Note pour le logiciel Sandboxie 5.74.0 fr (0 votes)
Bouton pour Noter Sandboxie 5.74.0 fr
 Commentaire :




A découvrir également ...


 
Les commentaires appartiennent à leurs auteurs. Nous ne sommes pas responsables de leur contenu.
Posté Commentaire en débat
Déposer un commentaire
Règles des commentaires*
Tous les commentaires doivent être approuvés par un Administrateur
Titre*
Nom*
Courriel*
Site internet*
Message*
Code de Confirmation*
0 + 5 = ?  
Entrez le résultat de l'expression
Maximum de tentatives que vous pouvez essayer : 10
Publicités
Qui est en ligne
Vous devez être connecté pour voir cette information.