Closed
Bug 712747
Opened 13 years ago
Closed 9 months ago
Clang Static Analysis: Assigned value is garbage or undefined netwerk/socket/nsSOCKSIOLayer.cpp
Categories
(Core :: Networking: Proxy, defect, P3)
Core
Networking: Proxy
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: decoder, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [necko-next])
The following report (in the URL field) has been generated by static analysis using Clang.
In this particular report, the problem is that the function | nsSOCKSSocketInfo::ReadNetAddr | does not handle the case where the | fam | parameter is not either | PR_AF_INET | or | PR_AF_INET6 |. I checked the code and this function only seems to be used twice and there INET/INET6 is used. Nevertheless, would it make sense to add an else branch covering the wrong usage? (Probably just setting addr to NULL and returning). If that doesn't make sense at all, just close this bug :)
Updated•9 years ago
|
Assignee: nobody → mcmanus
Whiteboard: [necko-active]
Updated•9 years ago
|
Whiteboard: [necko-active] → [necko-next]
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P2
Comment 2•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 3•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Component: Networking → Networking: Proxy
Comment 5•9 months ago
|
||
This can only be used with AF_INET and AF_INET6; if we don't understand the protocol we can't pull data from the reader for it, so simply not pulling anything is reasonable. We shouldn't clear addr
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•