CVE-2018-14822
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 · uneditedEntes EMG12 versions 2.57 and prior an information exposure through query strings vulnerability in the web interface has been identified, which may allow an attacker to impersonate a legitimate user and execute arbitrary code.
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 confidenceEntes EMG12 versions 2.57 and prior contain an information exposure vulnerability in the web interface where sensitive data (likely authentication credentials or session identifiers) is transmitted via URL query strings. This allows attackers to intercept this information, impersonate legitimate authenticated users, and execute arbitrary code on the affected system.
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<= 2.57CVSS 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.0/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 device model and firmware versionAccess the EMG12 web interface (typically via HTTP on ports 80/8080) and navigate to System Information, Status, or About page to locate the firmware version. Alternatively, check the device labeling or management console.Affected if The device is an Entes EMG12 with firmware version 2.57 or lower.
-
Verify web interface is network-accessibleAttempt to reach the device's web interface from a client system using the device's IP address on common HTTP ports (80, 443, 8080).Affected if The web interface responds to HTTP/HTTPS requests, indicating it is network-accessible.
-
Capture and inspect authentication trafficUse a browser proxy or network packet capture tool to intercept the HTTP traffic when logging into the web interface. Examine the login request (typically a GET or POST to the authentication endpoint) and subsequent requests.Affected if Authentication credentials, session identifiers, or other sensitive parameters appear in the URL query string rather than in the request body or HTTP headers.
-
Review access logs for exposed credentialsIf you have access to upstream proxy logs, firewall logs, or the device's own access logs, search for login or authentication-related URLs. Look for sensitive values in the query string portion of logged URLs.Affected if Logs contain URLs with usernames, passwords, session tokens, or similar sensitive data visible in the query string parameters.
You are affected if the device is an Entes EMG12 running firmware version 2.57 or lower and the web interface transmits authentication credentials or session identifiers via URL query strings.
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 dataRestrict web interface access to trusted networks, implement secure session management that avoids query string transmission of sensitive data, upgrade to a patched version if available, and monitor for exposed credentials in access logs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14822 — 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-14822 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