nccgroup / nccgroup/singularity

Missunderstanding about "multiple answers" attack strategy

Open
#61 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.3k
Forks
161
PR merge metrics
No merged PRs in 30d

Description

Hi! I have been using Singularity of Origin for some time and I was wondering whether you can help me answer some technical questions I did not succeed in solving so far.

I have been using the "Multiple answers" attack strategy multiple times and as indicated in the Wiki, one should set the "Target host" field to 0.0.0.0 on Unix and MacOS systems and to 127.0.0.1 on Windows systems. Is there a reason for this? I know that 0.0.0.0 "allows us to access the localhost on Linux and macOS systems" but why isn't 127.0.0.1 used on all systems?

Also, I am running these versions of Chrome (136.0.7103.59 ), Chromium (135.0.7049.95) and Firefox (137.0.2) on a machine with a Debian distribution and it seems like PNA is not enforced in any of these browsers when using 127.0.0.1 as the "Target host" and "First then second" rebinding strategy. This is different compared to what was reported before. Do you know whether there is a reason for this?

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

No source file or test is identified. Start by reviewing the Wiki guidance for the Multiple answers strategy and the reported behavior with 0.0.0.0, 127.0.0.1, and PNA in the listed Chrome, Chromium, and Firefox versions. Done means the platform-specific behavior and the apparent PNA discrepancy are explained or reproduced.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
networking, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.