CVE-2014-3804
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 av-centerd SOAP service in AlienVault OSSIM before 4.7.0 allows remote attackers to execute arbitrary commands via a crafted (1) update_system_info_debian_package, (2) ossec_task, (3) set_ossim_setup admin_ip, (4) sync_rserver, or (5) set_ossim_setup framework_ip request, a different vulnerability than CVE-2014-3805.
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 av-centerd SOAP service in AlienVault OSSIM before 4.7.0 contains a command injection vulnerability. Specific SOAP methods (update_system_info_debian_package, ossec_task, set_ossim_setup admin_ip, sync_rserver, and set_ossim_setup framework_ip) fail to properly sanitize user input, allowing remote unauthenticated attackers to inject and execute arbitrary OS commands on the target system.
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.6.1= 4.0= 4.0.3= 4.0.4= 4.1= 4.1.2= 4.1.3= 4.2= 4.2.2= 4.2.3= 4.3= 4.3.1CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Verify AlienVault OSSIM is installedLook for OSSIM installation by checking for the presence of alienvault-related packages or directories, such as running 'dpkg -l | grep alienvault' or 'rpm -qa | grep alienvault' on Linux systems, or checking for /etc/ossim/ossim_setup.confAffected if AlienVault OSSIM software is found on the system
-
Determine installed OSSIM versionRun 'alienvaultd --version' or check the version file at /etc/alienvault_version, or inspect the OSSIM database for the version stringAffected if The version number is 4.6.1 or lower, or matches any of these specific versions: 4.0, 4.0.3, 4.0.4, 4.1, 4.1.2, 4.1.3, 4.2, 4.2.2, 4.2.3, 4.3, or 4.3.1
-
Confirm av-centerd SOAP service is runningCheck if the av-centerd process is running with 'ps aux | grep av-centerd' or check if port 40007 (or the configured SOAP port) is listening with 'netstat -tulpn | grep -E "40007|av-center"'Affected if The av-centerd SOAP service is actively running and accepting connections
-
Check network exposure of the SOAP serviceReview firewall rules or iptables to determine if the av-centerd port is accessible from untrusted networks, or attempt a local connection to the SOAP endpoint on the configured portAffected if The av-centerd SOAP port is exposed to untrusted or external network segments
The system is affected if it runs AlienVault OSSIM version 4.6.1 or lower (or any of the specific listed versions) and the av-centerd SOAP service is accessible, because the listed SOAP methods accept unsanitized input leading to command injection.
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.
dbcve · scopedUpgrade AlienVault OSSIM to version 4.7.0 or later to obtain the patched code. Until upgrade is completed, restrict network access to the av-centerd SOAP service to minimize exposure.
4.7.0
- 1. Back up the current OSSIM configuration and database before initiating the upgrade process.
- 2. Review the AlienVault OSSIM 4.7.0 release notes for any prerequisites or specific upgrade instructions.
- 3. Ensure the system meets the hardware and software requirements for version 4.7.0.
- 4. Perform the upgrade to OSSIM version 4.7.0 or later using the official AlienVault upgrade procedure.
- 5. After upgrade, verify that the av-centerd SOAP service is running correctly.
- 6. Validate that the previously vulnerable SOAP endpoints (update_system_info_debian_package, ossec_task, set_ossim_setup admin_ip, sync_rserver, set_ossim_setup framework_ip) are no longer accepting arbitrary command input.
- 7. Review system logs to confirm no exploitation occurred prior to the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3804 — 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-3804 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