# CVE-2008-0536: Denial of service in n/a

> Remote attackers can cause a denial of service on Cisco SCE and Icon Labs Iconfidant SSH servers via malicious SSH traffic during management operations.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w62j-hhjm-mfjv

## What is CVE-2008-0536?

CVE-2008-0536 is a high-severity denial of service vulnerability in n/a, published on 22 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the SSH server in (1) Cisco Service Control Engine (SCE) 3.0.x before 3.0.7 and 3.1.x before 3.1.0, and (2) Icon Labs Iconfidant SSH before 2.3.8, allows remote attackers to cause a denial of service (management interface outage) via SSH traffic that occurs during management operations and triggers "illegal I/O operations," aka Bug ID CSCsh49563.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Cisco Service Control Engine, Icon-Labs Iconfidant Ssh.

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

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

## Is CVE-2008-0536 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-0534](https://insights.sbomify.com/CVE-2008-0534/): Denial of service in n/a (high 7.8)
- [CVE-2008-0535](https://insights.sbomify.com/CVE-2008-0535/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0536 is a high-severity denial of service vulnerability in n/a, published on 22 May 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-0536 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-0536/ (Markdown: https://insights.sbomify.com/CVE-2008-0536/index.md)
```

## Sources

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

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