# CVE-2008-1543: Hardcoded credentials in n/a

> Remote attackers can gain partial administrative access to Airspan WiMAX ProST devices using default credentials in the web management interface.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m7vg-gwqc-x898

## What is CVE-2008-1543?

CVE-2008-1543 is a high-severity vulnerability in n/a, published on 28 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Advanced User Interface Pages in the ProST Web Management component on the Airspan WiMAX ProST have a certain default User ID and password, which makes it easier for remote attackers to obtain partial administrative access, a different vulnerability than CVE-2008-1262.

Weakness: CWE-255

## Which versions are affected by CVE-2008-1543?

It affects 1 product.


Products: Airspan Prost Web Management.

## How do I fix CVE-2008-1543?

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

## Is CVE-2008-1543 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1543 and fix it if it is affected.

What it is: CVE-2008-1543 is a high-severity vulnerability in n/a, published on 28 Mar 2008. 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-2008-1543 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-2008-1543/ (Markdown: https://insights.sbomify.com/CVE-2008-1543/index.md)
```

## Sources

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

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