Ess RecApplication · Et X

CVE-2023-28382

HIGH · 8.1 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to after 1.4.3 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 ESS REC Agent Server Edition series allows an authenticated attacker to view or alter an arbitrary file on the server. Affected products and versions are as follows: ESS REC Agent Server Edition for Linux V1.0.0 to V1.4.3, ESS REC Agent Server Edition for Solaris V1.1.0 to V1.4.0, ESS REC Agent Server Edition for HP-UX V1.1.0 to V1.4.0, and ESS REC Agent Server Edition for AIX V1.2.0 to V1.4.1

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

A directory traversal vulnerability exists in ESS REC Agent Server Edition across Linux, Solaris, HP-UX, and AIX platforms. The flaw allows authenticated attackers to manipulate file path inputs using traversal sequences (e.g., '../') to access or modify arbitrary files on the server filesystem outside the intended directory boundaries.

MitigationApply vendor-supplied patches or upgrade to fixed versions when available. Implement strict input validation on file path parameters and restrict authenticated user permissions to minimize attack surface.

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
Ess RecApplication
Affected:>= 1.0.0, <= 1.4.3>= 1.1.0, <= 1.4.0>= 1.2.0, <= 1.4.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

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

  1. Confirm ESS REC Agent Server Edition installation
    Identify if ESS REC Agent Server Edition is installed on the system by checking for the product binaries, services, or installation directories typical for this software on Linux, Solaris, HP-UX, or AIX platforms
    Affected if The product is installed on any of the affected platforms (Linux, Solaris, HP-UX, AIX)
  2. Determine installed version
    Use the product's command-line interface, configuration file, or system package manager to retrieve the installed version number of ESS REC Agent Server Edition
    Affected if The installed version falls within any of these ranges: 1.0.0 to 1.4.3, 1.1.0 to 1.4.0, or 1.2.0 to 1.4.1
  3. Verify authentication is configured
    Check the server configuration to determine whether authentication is enabled for the ESS REC Agent Server, as the vulnerability requires an authenticated attacker
    Affected if Authentication is enabled and valid user accounts exist who could supply malicious file path inputs
  4. Assess network exposure
    Determine if the ESS REC Agent Server is accessible over the network, as the vulnerability can be exploited remotely by authenticated attackers
    Affected if The server is exposed on the network and accepts connections from untrusted sources

The environment is affected if ESS REC Agent Server Edition is installed on Linux, Solaris, HP-UX, or AIX with a version between 1.0.0 and 1.4.3, authentication is enabled, and the server is network-accessible to authenticated 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 1.4.3
Interim mitigation

Apply vendor-supplied patches or upgrade to fixed versions when available. Implement strict input validation on file path parameters and restrict authenticated user permissions to minimize attack surface.

Fix this in Ess Rec Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28382 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28382 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