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

deleting property in vm context has no effect #6287

Closed
deian opened this issue Apr 19, 2016 · 2 comments
Closed

deleting property in vm context has no effect #6287

deian opened this issue Apr 19, 2016 · 2 comments
Labels
vm Issues and PRs related to the vm subsystem.

Comments

@deian
Copy link
Member

deian commented Apr 19, 2016

  • Version: 4.4.3, 5.10.1
  • Platform: Arch Linux 4.5.0

Example failure:

const vm = require('vm');
const sbox = { };
vm.createContext(sbox);
vm.runInContext(`
  this.x = 'w00t';
  delete this.x;
`, sbox);

console.log(sbox); // { x: 'w00t' }

Expected sbox.x to be undefined.

@mscdex mscdex added the vm Issues and PRs related to the vm subsystem. label Apr 19, 2016
@jasnell
Copy link
Member

jasnell commented Apr 19, 2016

Related to #6283

AnnaMag added a commit to AnnaMag/node that referenced this issue Dec 14, 2016
Deleting property in the vm context has no effect
nodejs#6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.
AnnaMag added a commit to AnnaMag/node that referenced this issue Dec 14, 2016
Deleting property in the vm context has no effect
as reported in nodejs#6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.
AnnaMag added a commit to AnnaMag/node that referenced this issue Dec 16, 2016
Deleting property in the vm context has no effect
as reported in nodejs#6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.
italoacasas pushed a commit that referenced this issue Dec 18, 2016
Deleting property in the vm context has no effect
as reported in #6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: #10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
cjihrig pushed a commit to cjihrig/node that referenced this issue Dec 20, 2016
Deleting property in the vm context has no effect
as reported in nodejs#6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: nodejs#10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
cjihrig pushed a commit that referenced this issue Dec 20, 2016
Deleting property in the vm context has no effect
as reported in #6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: #10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this issue Jan 23, 2017
Deleting property in the vm context has no effect
as reported in #6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: #10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this issue Jan 24, 2017
Deleting property in the vm context has no effect
as reported in #6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: #10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
MylesBorins pushed a commit that referenced this issue Jan 31, 2017
Deleting property in the vm context has no effect
as reported in #6287
The test is moved to the known_issues and will be fixed
with the 5.5 V8 API changes.

PR-URL: #10272
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
fhinkel added a commit to fhinkel/node that referenced this issue Feb 10, 2017
In the implementation of the vm module,
if a property is successfully deleted
on the sandbox, we also need to delete it
on the global_proxy object. Therefore, we
must not call args.GetReturnValue().Set().

We only intercept, i.e., call
args.GetReturnValue().Set(), in the
DeleterCallback, if Delete() failed, e.g. because
the property was read only.

Fixes nodejs#6287
@fhinkel
Copy link
Member

fhinkel commented Feb 13, 2017

Fixed in #11266

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vm Issues and PRs related to the vm subsystem.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants