# CVE-2010-2029: Auth bypass in n/a

> Remote attackers can bypass authentication in Cybozu Office by using a user's cell phone ID to access and modify sensitive information.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qwhv-gv46-cghm

## What is CVE-2010-2029?

CVE-2010-2029 is a medium-severity authentication bypass vulnerability in n/a, published on 24 May 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cybozu Office 7 Ktai and Dotsales do not properly restrict access to the login page, which allows remote attackers to bypass authentication and obtain or modify sensitive information by using the unique ID of the user's cell phone.

Weakness: CWE-264

## Which versions are affected by CVE-2010-2029?

It affects 2 products.


Products: Cybozu Cybozu Dotsales, Cybozu Cybozu Office.

## How do I fix CVE-2010-2029?

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

## Is CVE-2010-2029 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2029 and fix it if it is affected.

What it is: CVE-2010-2029 is a medium-severity authentication bypass vulnerability in n/a, published on 24 May 2010. 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-2010-2029 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-2010-2029/ (Markdown: https://insights.sbomify.com/CVE-2010-2029/index.md)
```

## Sources

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

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