# CVE-2014-0364: Other in n/a

> Remote attackers can spoof IQ responses in the Smack XMPP API by crafting a specific attribute, bypassing verification checks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 30 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5xpq-f27x-7pw7

## What is CVE-2014-0364?

CVE-2014-0364 is a medium-severity vulnerability in n/a, published on 30 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ParseRoster component in the Ignite Realtime Smack XMPP API before 4.0.0-rc1 does not verify the from attribute of a roster-query IQ stanza, which allows remote attackers to spoof IQ responses via a crafted attribute.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Igniterealtime Smack.

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

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

## Is CVE-2014-0364 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0363](https://insights.sbomify.com/CVE-2014-0363/): Weak cryptography in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0364 is a medium-severity vulnerability in n/a, published on 30 Apr 2014. 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-0364 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-0364/ (Markdown: https://insights.sbomify.com/CVE-2014-0364/index.md)
```

## Sources

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

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