dbcve.org
Eds G503 FirmwareOperating system · Moxa

CVE-2023-5035

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-02
Fix available
A fix is available. Upgrade to 5.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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
A vulnerability has been identified in PT-G503 Series firmware versions prior to v5.2, where the Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the cookie to be transmitted in plaintext over an HTTP session. The vulnerability may lead to security risks, potentially exposing user session data to unauthorized access and manipulation.

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

The PT-G503 Series firmware versions prior to v5.2 fail to set the Secure attribute on sensitive cookies during HTTPS sessions, allowing these cookies to be transmitted in plaintext when the session降级到HTTP, potentially exposing user session data to interception and manipulation.

MitigationUpgrade PT-G503 Series firmware to v5.2 or later to ensure the Secure attribute is properly set on cookies, preventing plaintext transmission.

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
Eds G503 FirmwareOperating system
Affected:< 5.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify device model
    Log into the device web interface or check the device label/console to confirm the model is PT-G503 Series or Moxa Eds G503
    Affected if Device is a PT-G503 Series or Moxa Eds G503 model
  2. Check firmware version
    Access the device web interface (typically via HTTP/HTTPS at the device IP), navigate to System Settings or Device Info section to view the firmware version. Alternatively, check via console/SSH using 'show version' or similar command if available
    Affected if Firmware version is displayed as less than 5.2 (e.g., 5.1.x, 5.0.x, etc.)
  3. Verify HTTPS is enabled
    In the device web interface, check Network Settings or Security Settings to confirm HTTPS access is enabled for the management interface
    Affected if HTTPS is enabled and the device uses cookies for session management
  4. Inspect cookie headers
    Use a browser developer tool or packet capture (e.g., Wireshark) while logging into the device via HTTPS. In the browser, open DevTools > Network tab, reload the page, click on a request, and examine the Set-Cookie headers in the Response Headers
    Affected if Cookies are set without the 'Secure' attribute (cookies appear as 'name=value' without '; Secure' suffix) and HTTPS is in use

You are affected if the device is a PT-G503 Series (Moxa Eds G503) with firmware version prior to 5.2, and you use HTTPS access where cookies are transmitted without the Secure flag.

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.2 or later
Fixed in 5.2
Interim mitigation

Upgrade PT-G503 Series firmware to v5.2 or later to ensure the Secure attribute is properly set on cookies, preventing plaintext transmission.

Recommended fix High confidence

PT-G503 Series firmware v5.2

  1. Obtain the PT-G503 Series firmware v5.2 from Moxa's official website or authorized support channel
  2. Access the PT-G503 device web management interface
  3. Navigate to the firmware upgrade or system maintenance section
  4. Upload the v5.2 firmware file and initiate the upgrade process
  5. Allow the device to complete the firmware update and reboot
  6. Verify the firmware version has been updated to v5.2

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

Fix this in Eds G503 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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