dbcve.org
EyouApplication

CVE-2014-1203

CRITICAL · 9.8 CVSS v3.1 Published 2017-10-24
Fix available
A fix is available. Upgrade to 3.6 or later.
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
The get_login_ip_config_file function in Eyou Mail System before 3.6 allows remote attackers to execute arbitrary commands via shell metacharacters in the domain parameter to admin/domain/ip_login_set/d_ip_login_get.php.

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

Command injection vulnerability in Eyou Mail System before version 3.6 where the get_login_ip_config_file function in admin/domain/ip_login_set/d_ip_login_get.php fails to sanitize the domain parameter before passing it to a system call, allowing remote attackers to inject arbitrary shell commands via shell metacharacters.

MitigationUpgrade to Eyou Mail System 3.6 or later to obtain the patched version. If immediate upgrade is not feasible, implement strict input validation on the domain parameter to reject shell metacharacters and restrict network access to the admin interface.

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
EyouApplication
Affected:< 3.6

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Eyou Mail System installation
    Locate the Eyou Mail System installation directory on the server by checking common web root paths or reviewing web server configuration files (httpd.conf, nginx.conf) for the document root.
    Affected if Eyou Mail System is installed on the server.
  2. Determine installed version
    Check for a version file or banner within the Eyou installation directory. Common locations include a version.php file, a config file, or the main index page header.
    Affected if The installed version is lower than 3.6.
  3. Verify vulnerable script exists
    Check if the file admin/domain/ip_login_set/d_ip_login_get.php exists within the Eyou installation directory.
    Affected if The vulnerable PHP script file is present in the expected path.
  4. Confirm admin interface is reachable
    Verify network accessibility of the /admin/ path or admin interface URL for the Eyou Mail System installation.
    Affected if The admin interface is accessible via network (authenticated or unauthenticated).
  5. Inspect the vulnerable parameter handling
    Examine the get_login_ip_config_file function in the identified PHP file to confirm it processes a domain parameter without sanitization before system calls.
    Affected if The code passes the domain parameter directly to a system call without input validation.

A user is affected if Eyou Mail System version is below 3.6, the vulnerable PHP script exists, and the admin interface is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 3.6 or later
Fixed in 3.6
Interim mitigation

Upgrade to Eyou Mail System 3.6 or later to obtain the patched version. If immediate upgrade is not feasible, implement strict input validation on the domain parameter to reject shell metacharacters and restrict network access to the admin interface.

Recommended fix Moderate confidence

Eyou Mail System 3.6

  1. 1. Verify current Eyou Mail System version by checking the web interface or system files
  2. 2. If version is below 3.6, plan for upgrade to version 3.6 or later
  3. 3. Before upgrading, perform a complete backup of the Eyou Mail System database, configuration files, and邮件数据
  4. 4. Review Eyou Mail System 3.6 release notes for any migration requirements
  5. 5. Execute upgrade to Eyou Mail System version 3.6 or latest stable release
  6. 6. After upgrade, verify the admin/domain/ip_login_set/d_ip_login_get.php file has been updated
  7. 7. Test that the ip_login_set functionality works correctly post-upgrade
  8. 8. Validate that shell metacharacters in domain parameters are now properly sanitized
Caveat Review release notes for potential configuration or migration changes between pre-3.6 and 3.6 versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eyou Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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