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

Jump on uninitialized values #6

Closed
LinuxJedi opened this issue Feb 16, 2016 · 1 comment
Closed

Jump on uninitialized values #6

LinuxJedi opened this issue Feb 16, 2016 · 1 comment
Assignees

Comments

@LinuxJedi
Copy link
Contributor

The data element of the string variables in the configuration is unset at initialize time. This can cause startup failure in NGINX for certain allocators. You can reproduce this with the following when daemon and master_process is disabled in NGINX:

valgrind --malloc-fill=A5 --free-fill=DE sbin/nginx

I've attached a patch for this
conf_fix.diff.zip

@zimmerle zimmerle self-assigned this Feb 16, 2016
@zimmerle
Copy link
Contributor

Hi @LinuxJedi,

Thanks for the patch. It was merged into our master tree.

dennus pushed a commit to dennus/ModSecurity-nginx that referenced this issue Apr 23, 2018
…rity from headers_already_sent to develop

* commit 'f5dbf6a31d64da9932b3be24ba1dce616550cd3b':
  fix errors
  [*] fix test and special response processing on phase 3
  fix empty chunk problem
  remove unused typedef
  remove unused field from context
  fix forrmat
  [*] clear formatting
  remove useless function definition
  complete body processing without sending headers allready sent error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants