Opened 11 years ago
Closed 11 years ago
#370 closed defect (invalid)
Possible null pointer dereference?
Reported by: | Tomasz Kojm | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | nginx-core | Version: | 1.3.x |
Keywords: | Cc: | ||
uname -a: | |||
nginx -V: | nginx 1.4.1 |
Description
It seems there's a possibility of a null pointer dereference in ngx_http_upstream.c, see the attached patch against 1.4.1.
Thanks for your great work,
Tomasz Kojm
Attachments (1)
Change History (4)
by , 11 years ago
Attachment: | ngx_http_upstream.c.diff added |
---|
follow-up: 2 comment:1 by , 11 years ago
comment:2 by , 11 years ago
Replying to Maxim Dounin:
The r->cache is only created if there is u->pipe, so there shouldn't be a problem. Do you see the null pointer dereference in real life, or it's just an assumption based on reading the code?
Just based on the code - the other checks for u->pipe in that function misleaded me. Thanks for the quick feedback!
Thanks for ClamAV, BTW.
:-)
Note:
See TracTickets
for help on using tickets.
The r->cache is only created if there is u->pipe, so there shouldn't be a problem. Do you see the null pointer dereference in real life, or it's just an assumption based on reading the code?
Thanks for ClamAV, BTW.