# CVE-2012-1833: Missing authorization in n/a

> Remote attackers can bypass access restrictions and modify arbitrary object properties in Grails applications via crafted request parameters.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 28 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-74r6-f5w3-4rxg

## What is CVE-2012-1833?

CVE-2012-1833 is a medium-severity missing authorization vulnerability in n/a, published on 28 Sep 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware SpringSource Grails before 1.3.8, and 2.x before 2.0.2, does not properly restrict data binding, which might allow remote attackers to bypass intended access restrictions and modify arbitrary object properties via a crafted request parameter to an application.

Weakness: CWE-264

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

It affects 1 product.


Products: Springsource Grails.

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

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

## Is CVE-2012-1833 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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