Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mapped Network Drives Still Accessible Inside Sandbox #2629

Closed
vrxgaminginc opened this issue Jan 24, 2023 · 3 comments
Closed

Mapped Network Drives Still Accessible Inside Sandbox #2629

vrxgaminginc opened this issue Jan 24, 2023 · 3 comments
Labels
Issue: Reproduced Issue reproduced without uncertainties Status: Fixed in Next Build Fixed in the next Sandboxie version Workaround Temporary or alternative solution

Comments

@vrxgaminginc
Copy link

Describe what you noticed and did

  1. Map Network Drive (Y:) to a Remote System
  2. Create a new Hardened Sandbox with Data Protection
  3. Edit INI

BlockNetworkFiles=y
AllowNetworkAccess=<BlockNetAccess>,n

  1. Launch Windows Explorer from Sandboxie

EXPECT:
Y:\ Should not be accessible

ACTUAL:
Y:\ is accessible

How often did you encounter it so far?

always

Affected program

No relevant

Download link

Not relevant

Where is the program located?

Not relevant to my request.

Expected behavior

Y:\ Should not be accessible

What is your Windows edition and version?

Win 10 Pro

In which Windows account you have this problem?

A local or Microsoft account without special changes.

Please mention any installed security software

none

What version of Sandboxie are you running?

1.6.6

Is it a new installation of Sandboxie?

I recently did a new clean installation.

Is it a regression?

No response

In which sandbox type you have this problem?

In a hardened sandbox with data protection (red sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No response

Crash dump

No response

Trace log

No response

Sandboxie.ini configuration

Enabled=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#0423ee,ttl
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=9
AutoRecover=y
UseSecurityMode=y
UsePrivacyMode=y
BlockNetworkFiles=y
AllowNetworkAccess=<BlockNetAccess>,n
ClosedFilePath=<BlockNetDevices>,InternetAccessDevices
@vrxgaminginc vrxgaminginc added the Confirmation Pending Further confirmation is requested label Jan 24, 2023
@offhub
Copy link
Collaborator

offhub commented Jan 25, 2023

I can confirm this issue. The issue occurs if the RestrictDevices=y (or UseSecurityMode=y) option is enabled.

sbiemapdrv01.mp4

@isaak654 isaak654 added Issue: Reproduced Issue reproduced without uncertainties and removed Confirmation Pending Further confirmation is requested labels Jan 25, 2023
@DavidXanatos DavidXanatos added the Priority: High To be done as soon as possible label Jan 25, 2023
@DavidXanatos
Copy link
Member

DavidXanatos commented Jan 27, 2023

will be fixed in 1.7.1, ETA for release: Monday or so
until then you can remedy the issue with ClosedFilePath=\Device\Mup

@DavidXanatos DavidXanatos added Status: Fixed in Next Build Fixed in the next Sandboxie version Workaround Temporary or alternative solution and removed Priority: High To be done as soon as possible labels Jan 27, 2023
@DavidXanatos
Copy link
Member

the fix is already commited to github, but will only be active in release 1.7.1 as its in the driver which will need signing, the live preview builds 1.7.0a,b,c,... all use the 1.6.7 driver hence the fix will not be available in hose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Reproduced Issue reproduced without uncertainties Status: Fixed in Next Build Fixed in the next Sandboxie version Workaround Temporary or alternative solution
Projects
None yet
Development

No branches or pull requests

4 participants