# CVE-2007-3100: Denial of service in n/a

> Local attackers can cause a denial of service in open-iscsi by exploiting insecure permissions on a shared memory semaphore used for logging.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **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:** Yes
- **Published:** 14 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-3100, GHSA-jgp8-v927-5p6w

## What is CVE-2007-3100?

CVE-2007-3100 is a low-severity denial of service vulnerability in n/a, published on 14 Jun 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

usr/log.c in iscsid in open-iscsi (iscsi-initiator-utils) before 2.0-865 uses a semaphore with insecure permissions (world-writable/world-readable) for managing log messages using shared memory, which allows local users to cause a denial of service (hang) by grabbing the semaphore.

## Which versions are affected by CVE-2007-3100?

It affects 1 product.


Products: Redhat Open Iscsi.

## How do I fix CVE-2007-3100?

Upgrade to a fixed version.

## Is CVE-2007-3100 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3100 and fix it if it is affected.

What it is: CVE-2007-3100 is a low-severity denial of service vulnerability in n/a, published on 14 Jun 2007. 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-2007-3100 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-2007-3100/ (Markdown: https://insights.sbomify.com/CVE-2007-3100/index.md)
```

## Sources

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

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