# CVE-2018-7957: Missing authorization in Victoria-AL00

> Attackers can exploit an interface lacking proper authorization to obtain user location data on Huawei smartphones.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5j2f-65vx-6272

## What is CVE-2018-7957?

CVE-2018-7957 is a low-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. Victoria-AL00, published on 31 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei smartphones with software Victoria-AL00 8.0.0.336a(C00) have an information leakage vulnerability. Because an interface does not verify authorization correctly, attackers can exploit an application with the authorization of phone state to obtain user location additionally.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2018-7957?

It affects 1 product.


Products: Huawei Victoria-Al00 Firmware.

## How do I fix CVE-2018-7957?

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

## Is CVE-2018-7957 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7957 and fix it if it is affected.

What it is: CVE-2018-7957 is a low-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. Victoria-AL00, published on 31 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7957 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Victoria-AL00. 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-2018-7957/ (Markdown: https://insights.sbomify.com/CVE-2018-7957/index.md)
```

## Sources

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

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