# CVE-2012-0308: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions via CSRF, leading to account takeover and privilege escalation in Symantec Messaging Gateway.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8v6v-8fvr-82fp

## What is CVE-2012-0308?

CVE-2012-0308 is a medium-severity vulnerability in n/a, published on 29 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Symantec Messaging Gateway (SMG) before 10.0 allows remote attackers to hijack the authentication of administrators.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Symantec Messaging Gateway.

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

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

## Is CVE-2012-0308 being exploited?

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

Public exploit code:

- Symantec Messaging Gateway 9.5.3-3 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-6326](https://insights.sbomify.com/CVE-2017-6326/): Code injection in Messaging Gateway (critical 10.0)
- [CVE-2018-12242](https://insights.sbomify.com/CVE-2018-12242/): Auth bypass in Symantec Messaging Gateway (critical 9.8)
- [CVE-2018-12243](https://insights.sbomify.com/CVE-2018-12243/): XML external entity in Symantec Messaging Gateway (high 8.8)
- [CVE-2016-2204](https://insights.sbomify.com/CVE-2016-2204/): Command injection in n/a (high 8.2)
- [CVE-2012-3579](https://insights.sbomify.com/CVE-2012-3579/): Hardcoded credentials in n/a (high 7.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0308 is a medium-severity vulnerability in n/a, published on 29 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-0308 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-0308/ (Markdown: https://insights.sbomify.com/CVE-2012-0308/index.md)
```

## Sources

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

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