# CVE-2013-5364: Misconfiguration in n/a

> Local attackers can modify the Secunia CSI Agent configuration file due to insecure permissions, potentially leading to privilege escalation or unauthorized changes.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **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:** No
- **Published:** 26 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8hw4-j3wm-g228

## What is CVE-2013-5364?

CVE-2013-5364 is a low-severity vulnerability in n/a, published on 26 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Secunia CSI Agent 6.0.0.15017 and earlier, 6.0.1.1007 and earlier, and 7.0.0.21 and earlier, when running on Red Hat Linux, uses world-readable and world-writable permissions for /etc/csia_config.xml, which allows local users to change CSI Agent configuration by modifying this file.

Weakness: CWE-264

## Which versions are affected by CVE-2013-5364?

It affects 1 product.


Products: Secunia Csi Agent.

## How do I fix CVE-2013-5364?

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

## Is CVE-2013-5364 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5364 and fix it if it is affected.

What it is: CVE-2013-5364 is a low-severity vulnerability in n/a, published on 26 Jan 2014. 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-2013-5364 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-2013-5364/ (Markdown: https://insights.sbomify.com/CVE-2013-5364/index.md)
```

## Sources

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

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