feat: update templated plugin for CVE-2024-4956

[W0ngL1]

Hi @tooryx,

Here is the testbed PR: google/security-testbeds#148.

[leonardo-doyensec]

Hello @W0ngL1.
Thank you for your contribution. I'm noticing that the plugin lacks of a fingerprinting phase. Please implement it.
Moreover i think that the description field should contain an explanation of the issue. Please change it.

Feel free to reach out
~ Leonardo (Doyensec)

[W0ngL1]

Hi @leonardo-doyensec.

Should I create a new issue for this fingerprinting plugin?
And I've updated the description with reference to GHSA-6cgv-69mq-8w7x.

[leonardo-doyensec]

Hello @W0ngL1.
In order to implement a proper fingerprint all you need is a way to identify that the service that you are hitting is Nexus. Maybe a request to a non existing endpoint or a well-known one may reveal additional information on the running service.

[W0ngL1]

Hi @leonardo-doyensec.

I have a question regarding the workflow. Do I need to determine the version based on the fingerprint first, and then decide whether a vulnerability scan is possible?
From the previous project design, it seems like I may need to submit a fingerprint collector that covers all versions.

In that case, should I open a separate issue to track this work?

[leonardo-doyensec]

Hello @W0ngL1
The best option would be to find a way to fingerprint the exact version of the service running. It would be possible to parse the HTML of a page in order to understand the version.

What i'm mentioning here is fingerprint phase, not a fingerprint plugin. If you want to implement a fingerprint plugin you should follow the standard submission process.

[W0ngL1]

Copy that @leonardo-doyensec.

[W0ngL1]

Hi @leonardo-doyensec,

I've updated. If there are any issues, feel free to let me know.

[leonardo-doyensec]

LGTM
@tooryx we can merge this as well as google/security-testbeds#148

Reviewer: Leonardo (Doyensec)
Plugin: CVE-2024-4956
Drawbacks: None