# CVE-2013-4629: Auth bypass in n/a

> Remote authenticated users can hijack sessions on Huawei video conference units due to static session IDs, allowing unauthorized access to user accounts.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** 20 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2r86-h346-r99c

## What is CVE-2013-4629?

CVE-2013-4629 is a high-severity authentication bypass vulnerability in n/a, published on 20 Jun 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Huawei viewpoint VP9610 and VP9620 units for the Huawei Video Conference system do not update the Session ID upon successful establishment of a login session, which allows remote authenticated users to hijack sessions via an unspecified interception method.

Weakness: CWE-255

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

It affects 2 products.


Products: Huawei Vp 9610, Huawei Vp 9620.

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

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

## Is CVE-2013-4629 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4629 is a high-severity authentication bypass vulnerability in n/a, published on 20 Jun 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4629 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-4629/ (Markdown: https://insights.sbomify.com/CVE-2013-4629/index.md)
```

## Sources

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

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