# CVE-2000-0124: Security feature bypass in n/a

> Attackers can bypass web access restrictions in surfCONTROL SuperScout by using domains ending with a dot.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gh2j-73gh-h7q7

## What is CVE-2000-0124?

CVE-2000-0124 is a low-severity vulnerability in n/a, published on 8 Feb 2000. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

surfCONTROL SuperScout does not properly asign a category to web sites with a . (dot) at the end, which may allow users to bypass web access restrictions.

## Which versions are affected by CVE-2000-0124?

It affects 1 product.


Products: Surfcontrol Superscout.

## How do I fix CVE-2000-0124?

No fix has been published for CVE-2000-0124 yet. Limit exposure of the affected software until one is available.

## Is CVE-2000-0124 being exploited?

There is no known exploitation of CVE-2000-0124 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0124 and fix it if it is affected.

What it is: CVE-2000-0124 is a low-severity vulnerability in n/a, published on 8 Feb 2000. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2000-0124 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2000-0124/ (Markdown: https://insights.sbomify.com/CVE-2000-0124/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2000-0124
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2000-0124
- OSV: https://osv.dev/vulnerability/CVE-2000-0124

---
From sbomify Insights: https://insights.sbomify.com/CVE-2000-0124/
Summaries are generated and may contain mistakes; the official description above is the record.