dbcve.org
EdeployApplication · Redhat

CVE-2014-3702

CRITICAL · 9.1 CVSS v3.0 Published 2017-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Directory traversal vulnerability in eNovance eDeploy allows remote attackers to create arbitrary directories and files and consequently cause a denial of service (resource consumption) via a .. (dot dot) the session parameter.

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 · moderate confidence

eNovance eDeploy contains a directory traversal vulnerability where the session parameter accepts '..' sequences, allowing remote attackers to write files to arbitrary locations on the filesystem. This enables creation of malicious directories and files, leading to denial of service through resource consumption.

MitigationImplement strict input validation on the session parameter to reject path traversal sequences ('..'), sanitize all user-supplied paths, and enforce the application to operate within allowed directory boundaries.

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
EdeployApplication
Affected:= 0.1.0= 0.2.0= 1.4.0= 1.5.0= h.1.0.0= h.1.1.0= h.1.2.0= h.1.3.0

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if eDeploy is installed
    Locate eDeploy installation directories and binaries. Common paths include /opt/edeploy, /usr/share/edeploy, or check for eDeploy service processes running on the system using 'ps aux | grep eDeploy' or 'systemctl list-units | grep eDeploy'
    Affected if eDeploy software is present on the system
  2. Determine the installed eDeploy version
    Run 'edeploy --version' or check version files in installation directories such as /usr/share/edeploy/version, /opt/edeploy/VERSION, or look in RPM package metadata using 'rpm -qa | grep edeploy'
    Affected if The installed version matches 0.1.0, 0.2.0, 1.4.0, 1.5.0, h.1.0.0, h.1.1.0, h.1.2.0, or h.1.3.0
  3. Verify the session parameter handling is exposed
    Inspect web application configuration files (typically in /etc/edeploy, /opt/edeploy/conf, or within the application WAR/jar) for session parameter processing code. Check if the application exposes HTTP/HTTPS endpoints that accept session parameters without proper validation
    Affected if The application accepts session parameters via HTTP requests and processes them without explicit validation blocking '..' sequences
  4. Review application logs for path traversal attempts
    Examine eDeploy log files (commonly in /var/log/edeploy, /opt/edeploy/logs, or stdout/stderr logs) for patterns containing '..' in session parameters, unusual file creation events, or access to paths outside the designated upload directory
    Affected if Logs show session parameter values containing '..' sequences or unexpected file writes outside the intended directory

The environment is affected if eDeploy versions 0.1.0, 0.2.0, 1.4.0, 1.5.0, h.1.0.0, h.1.1.0, h.1.2.0, or h.1.3.0 are installed and the session parameter feature is exposed via HTTP endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the session parameter to reject path traversal sequences ('..'), sanitize all user-supplied paths, and enforce the application to operate within allowed directory boundaries.

Fix this in Edeploy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3702 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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