CVE-2018-25159
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 · uneditedEpross AVCON6 systems management platform contains an object-graph navigation language (OGNL) injection vulnerability that allows unauthenticated attackers to execute arbitrary commands by injecting malicious OGNL expressions. Attackers can send crafted requests to the login.action endpoint with OGNL payloads in the redirect parameter to instantiate ProcessBuilder objects and execute system commands with root privileges.
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 confidenceEpross AVCON6 systems management platform contains an OGNL injection vulnerability in the login.action endpoint. Attackers can inject malicious OGNL expressions through the redirect parameter to instantiate ProcessBuilder objects and execute arbitrary system commands with root privileges, achieving unauthenticated remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm AVCON6 installationLocate the AVCON6 installation directory or check for running services named 'AVCON' or 'avcon6' on the system. Common paths include /opt/avcon, C:\AVCON, or check running processes via 'ps aux | grep -i avcon' (Linux) or 'tasklist | findstr avcon' (Windows).Affected if AVCON6 system management platform is installed and running on the host
-
Identify AVCON6 versionCheck the version file or banner within the AVCON6 installation directory. Look for version.info, about.properties, or check the application banner when accessing the web interface. Compare your version to any known versions provided by the vendor.Affected if The installed version of AVCON6 matches or falls within the affected version range (if known)
-
Verify login.action endpoint accessibilityAttempt to access the login.action endpoint on the AVCON6 web server. Use a browser or curl: 'curl -k https://TARGET/avcon/login.action' or 'http://TARGET/avcon/login.action'.Affected if The login.action endpoint responds with an HTTP 200 status, indicating it is accessible and potentially vulnerable
-
Check if redirect parameter accepts input without authenticationSend a crafted request to login.action with the redirect parameter: 'curl -k "https://TARGET/avcon/login.action?redirect=Test"'. Verify the parameter is processed without requiring authentication.Affected if The redirect parameter accepts and reflects user input without any authentication requirement, indicating the pre-authentication flaw is present
A host is affected if AVCON6 is installed, the login.action endpoint is accessible, and the redirect parameter processes input without authentication, allowing OGNL 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.
From vendor dataApply vendor security patches immediately. If no patch is available, deploy a WAF with rules to block OGNL injection patterns and consider network segmentation to restrict access to the affected system until a proper fix is available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25159 — 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-2018-25159 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