dwisiswant0 / ppfuzz Goto Github PK

hi
i got this is error how to fix it

Please add -silent or -s option and only VULN or INFO should be the output.

Nuclei templates not work

I am using preinstalled version. I have chrome installed too but when i try to execute ppfuzz from /usr/local/bin it says binary not executable and when it is placed somewhere else it says command not found. I have also tried chmod +x ppfuzz command but still same error.

unresolved imports clap::crate_authors, clap::crate_description, clap::crate_name, clap::crate_version
--> src/parser.rs:5:3
|
5 | crate_authors,
| ^^^^^^^^^^^^^ no crate_authors in the root
6 | crate_description,
| ^^^^^^^^^^^^^^^^^ no crate_description in the root
7 | crate_name,
| ^^^^^^^^^^ no crate_name in the root
8 | crate_version,
| ^^^^^^^^^^^^^ no crate_version in the root

error: cannot determine resolution for the macro crate_name
--> src/parser.rs:30:4
|
30 | crate_name!(), "FILE", "[OPTIONS]"
| ^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_authors
--> src/parser.rs:33:12
|
33 | .author(crate_authors!())
| ^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_description
--> src/parser.rs:34:11
|
34 | .about(crate_description!())
| ^^^^^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_name
--> src/parser.rs:35:10
|
35 | .name(crate_name!())
| ^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_version
--> src/parser.rs:36:13
|
36 | .version(crate_version!())
| ^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

warning: use of deprecated macro load_yaml: Deprecated in Issue #3087, maybe clap::Parser would fit your use case?
--> src/parser.rs:27:14
|
27 | let yaml = load_yaml!("cli.yaml");
| ^^^^^^^^^
|
= note: #[warn(deprecated)] on by default

warning: use of deprecated macro clap::load_yaml: Deprecated in Issue #3087, maybe clap::Parser would fit your use case?
--> src/parser.rs:9:3
|
9 | load_yaml,
| ^^^^^^^^^

error[E0308]: mismatched types
--> src/parser.rs:32:23
|
32 | let app = App::from(yaml)
| ^^^^ expected struct App, found &yaml_rust::yaml::Yaml

Some errors have detailed explanations: E0308, E0432.
For more information about an error, try rustc --explain E0308.
warning: ppfuzz (lib) generated 2 warnings
error: could not compile ppfuzz due to 7 previous errors; 2 warnings emitted

Use https://github.com/rust-lang/rustfmt to format the code

Hi,
first of all I need to thank you for your effort made on this awesome tool.

Can you please delete the version number from the compiled binaries names?
We, in reconftw, trying to automate the installation of tools but if the binaries for every new version will have a different name, that's will complicate installing the latest version of ppfuzz.

for exemple the names can be as below:

ppfuzz-aarch64
ppfuzz-armv7
ppfuzz-linux
ppfuzz-linux-i386
ppfuzz-osx
ppfuzz-windows.exe

Otherwise, we need to update the installation script for every new ppfuzz version.
thanks in advnce
Bilel Eljaamii

Hello. I used the command cargo build --release for building the resources after cloning it in my directory. Everything went fine till nearly 175 resources, later I am getting the following error

Tungstenite allows remote attackers to cause a denial of service

The Tungstenite crate through 0.20.0 for Rust allows remote attackers to cause
a denial of service (minutes of CPU consumption) via an excessive length of an
HTTP header in a client handshake. The length affects both how many times a parse
is attempted (e.g., thousands of times) and the average amount of data for each
parse attempt (e.g., millions of bytes).

See advisory page for additional details.

Only ppfuzz 1.0.1 is available in cargo, while latest version being 1.0.2

ppfuzz -l list.txt

| x | x | / _..___
| | | | | |/ // /
|| || ||`//_/

Prototype Pollution Fuzzer
@dwisiswant0

[ERRO] Unable to launch browser: Request timed out..
[INFO] Use '-h' flag for more info about command.

There is an error when building from source code and from cargo.
Different one from this other issue
Here is the error:

Compiling ppfuzz v1.0.1
error[E0658]: binding by-move and by-ref in the same pattern is unstable
--> /home/jusepe/.cargo/registry/src/github.com-1ecc6299db9ec823/ppfuzz-1.0.1/src/fuzzer.rs:53:37
|
53 |         if let Ok((ref url, vuln, is_err, detail, gadgets)) = res {
|                    -------                ^^^^^^  ^^^^^^^ by-move pattern here
|                    |                      |
|                    |                      by-move pattern here
|                    by-ref pattern here
|
= note: see issue #68354 <https://github.com/rust-lang/rust/issues/68354> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `ppfuzz`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `ppfuzz v1.0.1`, intermediate artifacts can be found at `/tmp/cargo-installRpiuBb`

Caused by:
build failed

Cargo version:

cargo 1.46.0

Hello folks,

How i can fix this issue?
Regards :)

Can you help me to fix this error
Thanks

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Timeout', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/ppfuzz-0.0.1/src/browser.rs:23:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

yaml-rust is unmaintained.

The maintainer seems unreachable.

Many issues and pull requests have been submitted over the years
without any response.

Alternatives

Consider switching to the actively maintained yaml-rust2 fork of the original project:

• yaml-rust2
• yaml-rust2 @ crates.io)

See advisory page for additional details.

`cargo build --release

Compiling ppfuzz v1.0.1 (/Users/azhariramadhan/Documents/pentest-tools/reconftw/ppfuzz)
error[E0432]: unresolved imports clap::crate_authors, clap::crate_description, clap::crate_name, clap::crate_version
--> src/parser.rs:5:3
|
5 | crate_authors,
| ^^^^^^^^^^^^^ no crate_authors in the root
6 | crate_description,
| ^^^^^^^^^^^^^^^^^ no crate_description in the root
7 | crate_name,
| ^^^^^^^^^^ no crate_name in the root
8 | crate_version,
| ^^^^^^^^^^^^^ no crate_version in the root

error: cannot determine resolution for the macro crate_name
--> src/parser.rs:30:4
|
30 | crate_name!(), "FILE", "[OPTIONS]"
| ^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_authors
--> src/parser.rs:33:12
|
33 | .author(crate_authors!())
| ^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_description
--> src/parser.rs:34:11
|
34 | .about(crate_description!())
| ^^^^^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_name
--> src/parser.rs:35:10
|
35 | .name(crate_name!())
| ^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the macro crate_version
--> src/parser.rs:36:13
|
36 | .version(crate_version!())
| ^^^^^^^^^^^^^
|
= note: import resolution is stuck, try simplifying macro imports

error[E0308]: mismatched types
--> src/parser.rs:32:23
|
32 | let app = App::from(yaml)
| --------- ^^^^ expected struct App, found &yaml_rust::yaml::Yaml
| |
| arguments to this function are incorrect
|
note: associated function defined here

Some errors have detailed explanations: E0308, E0432.
For more information about an error, try rustc --explain E0308.
error: could not compile ppfuzz due to 7 previous errors
`

Chromium still running in the background after ppfuzz's scanning which ate the ram.

I was thinking of using this tool but this does not works in wsl and wsl2