dbcve.org
Elastic Computing PlatformApplication · Enomaly

CVE-2009-0390

HIGH · 7.2 CVSS v2.0 Published 2009-02-02
Fix available
A fix is available. Upgrade to after 2.1 or later.
See remediation →
77/100
Remediation priority · High
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
Argument injection vulnerability in Enomaly Elastic Computing Platform (ECP), formerly Enomalism, before 2.1.1 allows local users to send signals to arbitrary processes by populating the /tmp/enomalism2.pid file with command-line arguments for the kill program.

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 confidence

Argument injection vulnerability in Enomaly ECP allows local users to manipulate the /tmp/enomalism2.pid file to inject arbitrary command-line arguments to the kill program, enabling sending signals to arbitrary processes.

MitigationUpgrade to Enomaly ECP 2.1.1 or later which addresses the insecure pid file handling, or restrict write access to /tmp/enomalism2.pid to the application runtime user only.

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
Elastic Computing PlatformApplication
Affected:<= 2.1= 2.1

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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 checks

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

  1. Check Enomaly ECP version
    Locate the Enomaly ECP installation and determine the version number (typically found in version files, about dialogs, or package metadata)
    Affected if Version is 2.1 or any version <= 2.1
  2. Verify if Enomaly ECP process is running
    Check for the running Enomaly ECP process using process listing commands (ps, task manager) or by checking if /tmp/enomalism2.pid exists
    Affected if The application process is running and /tmp/enomalism2.pid exists
  3. Inspect /tmp/enomalism2.pid file permissions
    Check the ownership and permissions of /tmp/enomalism2.pid using 'ls -la /tmp/enomalism2.pid' or equivalent file permission inspection
    Affected if The pid file is writable by users other than the application runtime user (world-writable or group-writable)

A user is affected if running Enomaly ECP version 2.1 or earlier with the application active and the pid file writable by non-privileged users.

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
Upgrade available Upgrade to a release after 2.1
Interim mitigation

Upgrade to Enomaly ECP 2.1.1 or later which addresses the insecure pid file handling, or restrict write access to /tmp/enomalism2.pid to the application runtime user only.

Fix this in Elastic Computing Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-0390 — 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-2009-0390 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