# CVE-1999-1279: Information disclosure in n/a

> Users sharing the same Local APPC LU can view each other's shared folders due to an interaction between AS/400 and SNA Server.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 9 Mar 2002
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3qcq-w2m6-vwwx

## What is CVE-1999-1279?

CVE-1999-1279 is a medium-severity vulnerability in n/a, published on 9 Mar 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An interaction between the AS/400 shared folders feature and Microsoft SNA Server 3.0 and earlier allows users to view each other's folders when the users share the same Local APPC LU.

## Which versions are affected by CVE-1999-1279?

It affects 1 product.


Products: Microsoft Sna Server.

## How do I fix CVE-1999-1279?

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

## Is CVE-1999-1279 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1279 and fix it if it is affected.

What it is: CVE-1999-1279 is a medium-severity vulnerability in n/a, published on 9 Mar 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-1279 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-1999-1279/ (Markdown: https://insights.sbomify.com/CVE-1999-1279/index.md)
```

## Sources

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

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