Skip to content
New issue

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

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

Already on GitHub? # to your account

V-241788 fails to apply due to invalid registry key #918

Closed
General-Fault opened this issue Jun 21, 2021 · 2 comments · Fixed by #919
Closed

V-241788 fails to apply due to invalid registry key #918

General-Fault opened this issue Jun 21, 2021 · 2 comments · Fixed by #919
Assignees
Labels
bug Something isn't working
Milestone

Comments

@General-Fault
Copy link

Describe the bug
IISServer-10.0-2.2 rule V-241788 references an invalid registry key. This appears to be a mistake in the STIG data.

"HKEY_LOCAL_MACHINE\CurrentControlSet\Services\HTTP\Parameters"
should be
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters"

To Reproduce
Create a configuration that applies the IISServer 10.0 rules.
Apply the configuration.
Note error:

VERBOSE: [CBARNES-DEPLOY]: LCM: [ End Set ] [[Registry][V-241788][low][SRG-APP-000266-WSR-000159]::[IisServer]IisServerSettings] in 0.1720 seconds.
PowerShell DSC resource MSFT_RegistryResource failed to execute Set-TargetResource functionality with error message: Exception calling "CreateSubKey" with "1" argument(s): "The parameter is
incorrect.
"
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : [OBFUSCATED]

Expected behavior
The rule should be applied. The value HKEY_LOCAL_MACHINE\CurrentControlSet\Services\HTTP\Parameters:DisableServerHeader = 1.

@erjenkin
Copy link
Contributor

Hello @General-Fault,

Thanks for the issue. Looking into this now, should have a fix in place shortly.

Thanks,

Eric

@erjenkin erjenkin self-assigned this Jun 22, 2021
@erjenkin erjenkin added this to the 4.10.0 milestone Jun 22, 2021
@erjenkin erjenkin added the bug Something isn't working label Jun 22, 2021
@erjenkin erjenkin linked a pull request Jul 1, 2021 that will close this issue
5 tasks
@erjenkin erjenkin closed this as completed Jul 6, 2021
@erjenkin
Copy link
Contributor

erjenkin commented Jul 6, 2021

fix has been merged, will be released with PowerSTIG 4.10.0

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants