# CVE-2013-2310: SoftBank Wi-Fi Spot Configuration Software, as used on SoftBank SHARP 3G handsets, SoftBank Panasonic 3G handsets, SoftBank NEC 3G handsets,


- **Severity:** Low 3.3 (`AV:A/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7mg4-jhxw-pmc3

## What is CVE-2013-2310?

CVE-2013-2310 is a low-severity vulnerability in n/a, published on 17 Jun 2013. 

### Official description

SoftBank Wi-Fi Spot Configuration Software, as used on SoftBank SHARP 3G handsets, SoftBank Panasonic 3G handsets, SoftBank NEC 3G handsets, SoftBank Samsung 3G handsets, SoftBank mobile Wi-Fi routers, SoftBank Android smartphones with the Wi-Fi application before 1.7.1, SoftBank Windows Mobile smartphones with the WISPrClient application before 1.3.1, SoftBank Disney Mobile Android smartphones with the Wi-Fi application before 1.7.1, and WILLCOM Android smartphones with the Wi-Fi application before 1.7.1, does not properly connect to access points, which allows remote attackers to obtain sensitive information by leveraging access to an 802.11 network.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-2310?

It affects 13 products.


Products: Softbank Android Smartphone, Softbank Disney Mobile Android Smartphone, Softbank Mobile Wi-Fi Router, Softbank Nec 3g Handset, Softbank Panasonic 3g Handset, Softbank Samsung 3g Handset, Softbank Sharp 3g Handset, Softbank Wi-Fi Application, Softbank Wi-Fi Spot Configuration Software, Softbank Windows Mobile Smartphone, Softbank Wisprclient, Willcom-Inc Android Smartphone, Willcom-Inc Wi-Fi Application.

## How do I fix CVE-2013-2310?

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

## Is CVE-2013-2310 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2310 and fix it if it is affected.

What it is: CVE-2013-2310 is a low-severity vulnerability in n/a, published on 17 Jun 2013. 
Exploitation: There is no known exploitation of CVE-2013-2310 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-2013-2310/ (Markdown: https://insights.sbomify.com/CVE-2013-2310/index.md)
```

## Sources

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

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