# CVE-2013-3505: Missing authorization in n/a

> Authenticated users can bypass access restrictions to read log and configuration files in GroundWork Monitor Enterprise.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/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:** 8 May 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5qmf-g5m5-xxgr

## What is CVE-2013-3505?

CVE-2013-3505 is a medium-severity missing authorization vulnerability in n/a, published on 8 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Nagios-App component in GroundWork Monitor Enterprise 6.7.0 allows remote authenticated users to bypass intended access restrictions via a direct request for a (1) log file or (2) configuration file.

Weakness: CWE-255

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

It affects 1 product.


Products: Gwos Groundwork Monitor.

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

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

## Is CVE-2013-3505 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3499](https://insights.sbomify.com/CVE-2013-3499/): Auth bypass in n/a (high 7.5)
- [CVE-2013-3500](https://insights.sbomify.com/CVE-2013-3500/): Privilege escalation in n/a (high 7.5)
- [CVE-2013-3506](https://insights.sbomify.com/CVE-2013-3506/): Code injection in n/a (high 7.5)
- [CVE-2013-3513](https://insights.sbomify.com/CVE-2013-3513/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-3502](https://insights.sbomify.com/CVE-2013-3502/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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