# CVE-2014-9504: Missing authorization in n/a

> Remote attackers can access child groups in Drupal Open Atrium due to improper membership inheritance in the OG Subgroups module.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hg4v-rxmf-r8x5

## What is CVE-2014-9504?

CVE-2014-9504 is a high-severity missing authorization vulnerability in n/a, published on 1 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OG Subgroups module, when used with the Open Atrium module 7.x-2.x before 7.x-2.26 for Drupal, allows remote attackers to access child groups via vectors related to membership inheritance.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2014-9504?

It affects 1 product.


Products: Open Atrium Project Open Atrium.

## How do I fix CVE-2014-9504?

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

## Is CVE-2014-9504 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9502](https://insights.sbomify.com/CVE-2014-9502/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2014-9503](https://insights.sbomify.com/CVE-2014-9503/): Missing authorization in n/a (medium 6.5)
- [CVE-2014-8736](https://insights.sbomify.com/CVE-2014-8736/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9504 and fix it if it is affected.

What it is: CVE-2014-9504 is a high-severity missing authorization vulnerability in n/a, published on 1 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9504 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-2014-9504/ (Markdown: https://insights.sbomify.com/CVE-2014-9504/index.md)
```

## Sources

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

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