# CVE-2012-4518: Misconfiguration in n/a

> Local attackers can overwrite log or port files due to world-writable permissions in ibacm, potentially disrupting InfiniBand access management.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/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:** 22 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2012-5637, GHSA-wwq4-mmvc-j357

## What is CVE-2012-4518?

CVE-2012-4518 is a low-severity vulnerability in n/a, published on 22 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ibacm 1.0.7 creates files with world-writable permissions, which allows local users to overwrite the ib_acm daemon log or ibacm.port file.

Weakness: CWE-264

## Which versions are affected by CVE-2012-4518?

It affects 1 product.


Products: Openfabrics Ibacm.

## How do I fix CVE-2012-4518?

Apply the vendor's patch.

## Is CVE-2012-4518 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4517](https://insights.sbomify.com/CVE-2012-4517/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4518 and fix it if it is affected.

What it is: CVE-2012-4518 is a low-severity vulnerability in n/a, published on 22 Oct 2012. 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-2012-4518 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-2012-4518/ (Markdown: https://insights.sbomify.com/CVE-2012-4518/index.md)
```

## Sources

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

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