CyberSecBulletin
CVE-2023-37862NVD status: Modified

WP 6070-WVPS: Missing Authorization

Published Updated By the CyberSecBulletin desk

CVE-2023-37862 is a high-severity missing authorization vulnerability in WP 6070-WVPS from Phoenix Contact, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.0.10 as the first without the flaw, so updating WP 6070-WVPS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update WP 6070-WVPS to 4.0.10 or a later version.
  2. Update WP 6101-WXPS to 4.0.10 or a later version.
  3. Update WP 6121-WXPS to 4.0.10 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
PHOENIX CONTACTWP 6070-WVPSbefore 4.0.104.0.10
PHOENIX CONTACTWP 6101-WXPSbefore 4.0.104.0.10
PHOENIX CONTACTWP 6121-WXPSbefore 4.0.104.0.10
PHOENIX CONTACTWP 6156-WHPSbefore 4.0.104.0.10
PHOENIX CONTACTWP 6185-WHPSbefore 4.0.104.0.10
PHOENIX CONTACTWP 6215-WHPSbefore 4.0.104.0.10
Phoenixcontactwp_6070-wvpsbefore 4.0.104.0.10
Phoenixcontactwp_6101-wxpsbefore 4.0.104.0.10
Phoenixcontactwp_6121-wxpsbefore 4.0.104.0.10
Phoenixcontactwp_6156-whpsbefore 4.0.104.0.10
Phoenixcontactwp_6185-whpsbefore 4.0.104.0.10
Phoenixcontactwp_6215-whpsbefore 4.0.104.0.10
PhoenixcontactWP 6070-wvps Firmwarebefore 4.0.104.0.10
PhoenixcontactWP 6101-wxps Firmwarebefore 4.0.104.0.10
PhoenixcontactWP 6121-wxps Firmwarebefore 4.0.104.0.10
PhoenixcontactWP 6156-whps Firmwarebefore 4.0.104.0.10
PhoenixcontactWP 6185-whps Firmwarebefore 4.0.104.0.10
PhoenixcontactWP 6215-whps Firmwarebefore 4.0.104.0.10

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L. Scored by CNA (cert.vde.com).

Official description

In PHOENIX CONTACTs WP 6xxx series web panels in versions prior to 4.0.10 an unauthenticated remote attacker can access upload-functions of the HTTP API. This might cause certificate errors for SSL-connections and might result in a partial denial-of-service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in WP 6070-WVPS

All WP 6070-WVPS vulnerabilities

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.