github-vet / github-vet/rangeloop-pointer-findings
lunaisnotaboy/niiverse: handlers.go; 8 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [lunaisnotaboy/niiverse](https://www.github.com/lunaisnotaboy/niiverse) at [handlers.go](https://github.com/lunaisnotaboy/niiverse/blob/218f4b54016d2b5db139fc91727f40a2b5dad09b/handlers.go#L714-L721)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
>
[Click here to see the code in its original context.](https://github.com/lunaisnotaboy/niiverse/blob/218f4b54016d2b5db139fc91727f40a2b5dad09b/handlers.go#L714-L721)
Click here to show the 8 line(s) of Go which triggered the analyzer.
```go
for _, user := range users {
stmt, err = db.Prepare("INSERT INTO group_members (user, conversation) VALUES (?, ?)")
if err != nil {
http.Error(w, err.Error(), http.StatusInternalServerError)
return
}
stmt.Exec(&user, &conversationID)
}
```
Click here to show extra information the analyzer produced.
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
root signature {Exec 2} was not found in the callgraph; reference was passed directly to third-party code
```
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 218f4b54016d2b5db139fc91727f40a2b5dad09b
Contributor guide
No contributing guide indexed for this repository
Research direction
Read handlers.go at lines 714-721 and inspect the surrounding handler and database call context. Determine whether the range-loop user reference can cause an actual problem, then classify the finding as Bug, Mitigated, or Desirable Behavior using the linked classification guidance and leave the corresponding reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100