mandatoryprogrammer / mandatoryprogrammer/sonar.js

Failing to recognize a Web server

Open
#22 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
551
Forks
76
PR merge metrics
No merged PRs in 30d

Description

Hello,

After updating the fingerprint file with a custom signature and running 'example.htm', I got the following error message:

`WebSocket connection to 'ws://192.168.0.23/318869b9-5f94-2a3c-fb65-ae2b132dc4d5' failed: Error during WebSocket handshake: Unexpected response code: 404`

As a further test, I modified the Sonar.js file and replaced the function 'sonar.generate_random_id()' for a static string, in order to obtain a 200 HTTP response code rather than a 404 and I obtained the following error message:

`WebSocket connection to 'ws://192.168.0.23/exploitable_script.php' failed: Error during WebSocket handshake: Unexpected response code: 200`

Thoughts?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the custom fingerprint file, example.htm, and Sonar.js, especially sonar.generate_random_id(). Reproduce the WebSocket handshake with the reported 404 and 200 responses, then trace how those responses affect web-server recognition. Done means the expected recognition behavior and the required change are confirmed by a repeatable test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.