This should end with something like: /hello?message=hello_world, where hello_world will be fuzzed.
But the actual behavior is just generating: /hello, because the parameter message is not defined in path of the endpoint.
Originally created by @starek4 on GitHub (Oct 28, 2019).
Originally assigned to: @starek4 on GitHub.
Some attributes may be documented as query attributes, but they do not have to be in the path of the specific endpoint.
Simple example:
```
paths:
/hello:
get:
description: Hello
summary: Hello summary
parameters:
- name: message
in: query
required: true
type: string
description: hello message
responses:
200:
description: OK
```
This **should** end with something like:
`/hello?message=hello_world`, where `hello_world` will be fuzzed.
But the **actual behavior** is just generating:
`/hello`, because the parameter message is not defined in path of the endpoint.
adam
added the bug label 2025-12-31 16:38:57 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @starek4 on GitHub (Oct 28, 2019).
Originally assigned to: @starek4 on GitHub.
Some attributes may be documented as query attributes, but they do not have to be in the path of the specific endpoint.
Simple example:
This should end with something like:
/hello?message=hello_world, wherehello_worldwill be fuzzed.But the actual behavior is just generating:
/hello, because the parameter message is not defined in path of the endpoint.@starek4 commented on GitHub (Oct 30, 2019):
Implemented by https://github.com/ysoftdevs/wapifuzz/pull/7