dbcve.org
Officeconnect 1820 24g Poe\+ \(185w\) Switch J9983a FirmwareOperating system · Hp

CVE-2022-37934

HIGH · 7.5 CVSS v3.1 Published 2023-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A potential security vulnerability has been identified in HPE OfficeConnect 1820, and 1850 switch series. The vulnerability could be remotely exploited to allow remote directory traversal in HPE OfficeConnect 1820 switch series version PT.02.17 and below, HPE OfficeConnect 1850 switch series version PC.01.23 and below, and HPE OfficeConnect 1850 (10G aggregator) switch version PO.01.22 and below.

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

A remote directory traversal vulnerability in HPE OfficeConnect 1820 and 1850 switch series allows unauthenticated attackers to access arbitrary files on the device filesystem via directory traversal sequences in HTTP requests.

MitigationUpdate to patched firmware versions above PT.02.17 for 1820 series, PC.01.23 for 1850 series, and PO.01.22 for 1850 10G aggregator. If immediate patching is not feasible, restrict network access to the management interface and consider a web application firewall as a compensating control.

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
Officeconnect 1820 24g Poe\+ \(185w\) Switch J9983a FirmwareOperating system
Affected:< pt.02.17
Officeconnect 1820 48g Poe\+ \(370w\) Switch J9984a FirmwareOperating system
Affected:< pt.02.17
Officeconnect 1820 8g Poe\+ \(65w\) Switch J9982a FirmwareOperating system
Affected:< pt.02.17
Officeconnect 1820 8g Switch J9979a FirmwareOperating system
Affected:< pt.02.17
Officeconnect 1850 24g 2xgt FirmwareOperating system
Affected:< pc.01.23
Officeconnect 1850 24g 2xgt Poe\+ FirmwareOperating system
Affected:< pc.01.23
Officeconnect 1850 2xgt\/spf\+ FirmwareOperating system
Affected:< po.01.22
Officeconnect 1850 48g 4xgt FirmwareOperating system
Affected:< pc.01.23

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. Identify the device model
    Access the switch web interface or check the device label/model number. Look for HPE OfficeConnect 1820 or 1850 series switches (J9983a, J9984a, J9982a, J9979a, or 1850 variants).
    Affected if The device is an HPE OfficeConnect 1820 or 1850 switch series.
  2. Check the firmware version
    Log into the switch web interface and navigate to the Maintenance or System Information page to view the installed firmware version. Alternatively, access the CLI and use 'show version' or 'show flash' commands.
    Affected if The firmware version cannot be determined or is not visible.
  3. Compare version against vulnerability thresholds
    For 1820 series (J9983a, J9984a, J9982a, J9979a), compare your firmware version to pt.02.17. For 1850 24g/48g variants, compare to pc.01.23. For 1850 2xgt/sfp+, compare to po.01.22.
    Affected if Your installed firmware version is below pt.02.17 for 1820 series, below pc.01.23 for 1850 24g/48g, or below po.01.22 for 1850 2xgt/sfp+.
  4. Verify web management interface accessibility
    Confirm that the switch HTTP/HTTPS management interface is reachable from your network. Attempt to access the login page via browser or curl command.
    Affected if The web interface is exposed and reachable.

You are affected if you have an HPE OfficeConnect 1820 or 1850 switch running firmware versions below pt.02.17, pc.01.23, or po.01.22 respectively, and the web management interface is accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to patched firmware versions above PT.02.17 for 1820 series, PC.01.23 for 1850 series, and PO.01.22 for 1850 10G aggregator. If immediate patching is not feasible, restrict network access to the management interface and consider a web application firewall as a compensating control.

Recommended fix High confidence

OfficeConnect 1820 series: PT.02.17 or later; OfficeConnect 1850 series: PC.01.23 or later; OfficeConnect 1850 (10G aggregator): PO.01.22 or later

  1. 1. Identify the specific HPE OfficeConnect switch model from the affected list (1820 or 1850 series).
  2. 2. Determine the current firmware version by accessing the switch web interface or CLI.
  3. 3. Download the appropriate firmware update from HPE support.hpe.com for your specific switch model.
  4. 4. For OfficeConnect 1820 series switches: upgrade to firmware version PT.02.17 or later.
  5. 5. For OfficeConnect 1850 series switches: upgrade to firmware version PC.01.23 or later.
  6. 6. For OfficeConnect 1850 (10G aggregator) switches: upgrade to firmware version PO.01.22 or later.
  7. 7. Upload the firmware through the switch web interface (System > Firmware Upload) or CLI.
  8. 8. Reboot the switch to apply the new firmware.
Caveat Review HPE release notes for any configuration changes or functionality differences in the new firmware version before upgrading

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

Fix this in Officeconnect 1820 24g Poe\+ \(185w\) Switch J9983a Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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