Hey, great lab. Thanks for taking the time to make it. In my case, the IP you referenc

Fixed <a href="https://github.com/dhmosfunk/CVE-2023-25690-POC/pull/2" data-hovercard-

Thank you <a class="user-mention notranslate" data-hovercard-type="user" data-hovercar

Sorry, this is the link : <a href="https://portswigger.net/research/making-http-header

Bad IP Reference in http.conf about cve-2023-25690-poc HOT 5 CLOSED

dhmosfunk commented on June 16, 2024 1

Bad IP Reference in http.conf

from cve-2023-25690-poc.

Comments (5)

cocoh-23 commented on June 16, 2024 1

I am making a pull request, feel free to accept it or not.

Thank you again for this lab!

from cve-2023-25690-poc.

dhmosfunk commented on June 16, 2024

Fixed Pull request 2.

from cve-2023-25690-poc.

cocoh-23 commented on June 16, 2024

Thank you @dhmosfunk. I have a question, have you tried to achieve Response Queue Poisoning with this behaviour? I leave you a nice link which i'll be trying in the next days. I believe this attack vector (https://portswigger.net/web-security/request-smuggling/advanced/response-queue-poisoning) could raise the impact of the vuln. if it's being hard to identify internal endpoints. Cheers

from cve-2023-25690-poc.

cocoh-23 commented on June 16, 2024

Sorry, this is the link : https://portswigger.net/research/making-http-header-injection-critical-via-response-queue-poisoning

from cve-2023-25690-poc.

dhmosfunk commented on June 16, 2024

Yeah, I think if we can manage to configure the reverse proxy in order to expect only one response per request maybe we can reproduce the HTTP response queue poisoning.