dbcve.org
IviewApplication · Advantech

CVE-2023-52335

HIGH · 7.5 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 5.7.04.6752 or later.
See remediation →
84/100
Remediation priority · High
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
Advantech iView ConfigurationServlet SQL Injection Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Advantech iView. Authentication is not required to exploit this vulnerability. The specific flaw exists within the ConfigurationServlet servlet, which listens on TCP port 8080 by default. When parsing the column_value element, the process does not properly validate a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-17863.

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

This is an unauthenticated SQL injection vulnerability in Advantech iView's ConfigurationServlet (TCP port 8080). The flaw exists in the parsing of the column_value element, which is not properly validated before being used in SQL query construction. Attackers can exploit this to inject malicious SQL and disclose stored credentials and other sensitive information.

MitigationApply the vendor patch when available. If no patch exists, restrict network access to port 8080 via firewall or network segmentation, and implement WAF rules to detect and block SQL injection attempts.

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
IviewApplication
Affected:< 5.7.04.6752

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify Advantech iView is installed
    Check for iView installation directory (default: C:\Program Files\Advantech\iView) or look for process named 'iViewServer.exe' or similar Java processes listening on port 8080 using 'netstat -ano | findstr :8080'
    Affected if iView is installed and port 8080 is listening
  2. Confirm the installed version
    Locate the iView version file or check the application GUI/About dialog for version number, typically found in installation directory or startup logs
    Affected if Installed version is lower than 5.7.04.6752
  3. Verify ConfigurationServlet is accessible
    Attempt HTTP access to port 8080 and check if ConfigurationServlet endpoint responds. Use curl or browser: http://<target>:8080/ConfigurationServlet
    Affected if ConfigurationServlet responds on port 8080 without authentication required
  4. Check for unauthenticated access to configuration endpoints
    Review if the ConfigurationServlet allows unauthenticated access by checking HTTP response codes on port 8080 endpoints without providing credentials
    Affected if HTTP 200 response is returned without authentication on configuration endpoints

User is affected if Advantech iView is running with version below 5.7.04.6752 and ConfigurationServlet on port 8080 is network-accessible without authentication.

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 5.7.04.6752 or later
Fixed in 5.7.04.6752
Interim mitigation

Apply the vendor patch when available. If no patch exists, restrict network access to port 8080 via firewall or network segmentation, and implement WAF rules to detect and block SQL injection attempts.

Recommended fix Moderate confidence

5.7.04.6752

  1. 1. Back up the current iView installation and database before proceeding with any upgrade.
  2. 2. Download Advantech iView version 5.7.04.6752 or later from the official Advantech support website (www.advantech.com).
  3. 3. Stop the iView service if it is currently running.
  4. 4. Install the updated version following the standard upgrade procedure documented in the iView administration guide.
  5. 5. Verify the ConfigurationServlet version and ensure the SQL injection vulnerability is no longer present.
  6. 6. Restart the iView service and confirm normal operation.
  7. 7. Test that the column_value parameter in ConfigurationServlet now properly validates input and does not allow SQL injection.

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

Fix this in Iview Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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