CVE-2014-0364
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ParseRoster component in the Ignite Realtime Smack XMPP API before version 4.0.0-rc1 fails to verify the 'from' attribute of roster-query IQ stanzas. This allows remote attackers to send spoofed IQ responses by including a crafted 'from' attribute, potentially leading to unauthorized roster manipulation or information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Smack XMPP library fileSearch for JAR files containing 'smack' in your application classpath or lib directory, such as smack-x.x.x.jar or similar naming patternsAffected if A smack JAR file exists with version below 4.0.0 in the filename
-
Check the JAR manifest versionOpen the META-INF/MANIFEST.MF file inside the smack JAR and look for the Implementation-Version or Bundle-Version attributeAffected if The version specified is less than 4.0.0 or the manifest shows no version attribute with a smack JAR present
-
Verify dependency configurationIf using Maven, Gradle, or another build tool, inspect your pom.xml or build.gradle file for the smack dependency declaration and note the specified versionAffected if The dependency version is declared as less than 4.0.0 (for example, 3.x.x, 3.4.x, etc.)
-
Confirm ParseRoster is in useSearch your codebase for imports or references to org.jivesoftware.smackx.roxcell.RosterPacketExtension or roster-related parsing logic, which indicates the ParseRoster component is being utilizedAffected if Your application parses or handles XMPP roster queries and uses a Smack version below 4.0.0
Your environment is affected if the Smack XMPP library version is below 4.0.0 and your application processes roster-query IQ stanzas.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.0.0
Upgrade to Smack XMPP API 4.0.0-rc1 or later which implements proper 'from' attribute validation in the ParseRoster component.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data