CVE-2005-2626 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2005-2626 and fix it if it is affected.
What it is: CVE-2005-2626 is a critical vulnerability in n/a, published on 19 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2626 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-2005-2626/ (Markdown: https://insights.sbomify.com/CVE-2005-2626/index.md)
Remote attackers can exploit unprintable characters in SSIDs to cause unspecified impacts in Kismet wireless network detectors.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2005-2626?
CVE-2005-2626 is a critical vulnerability in n/a, published on 19 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Unspecified vulnerability in Kismet before 2005-08-R1 allows remote attackers to have an unknown impact via unprintable characters in the SSID.
Which versions are affected by CVE-2005-2626?
It affects 1 product.
Products include Kismet Kismet.
How do I fix CVE-2005-2626?
Upgrade to a fixed version.
Is CVE-2005-2626 being exploited?
There is no known exploitation of CVE-2005-2626 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-xxx9-446j-m3xj.