Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
PUP 4.0.0
-
Windows 2012 R2 agent
-
2
-
Windows 2016-01-13
-
Reviewed
-
Attempting to read REG_BINARY registry data would previously cause Puppet to crash on Windows. This no longer occurs.
Description
On a Windows 2012 R2 node, the command: "puppet resource package --trace"
generates the following error:
Debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist[0m
[1;31mError: Could not run: undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
C:/Program Files/Puppet Labs/Puppet/puppet/lib/puppet/util/windows/registry.rb:216:in `block in read'
Line 216 in puppet/util/windows/registry.rb is this:
result = [ type, data.read_bytes(0, byte_length) ]
That line uses "data.read_bytes", but all the other lines in that case statement use "data_ptr.read_bytes". This appears to be an oversight.
Attachments
Issue Links
- relates to
-
PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
-
- Closed
-
- links to