Skip to content
Fencer Intel
critical 9.8

CVE-2023-37265 json

Incorrect identification of source IP addresses in CasaOS

published 3y ago modified 2mo ago also GHSA-vjh7-5r6x-xh6g , GO-2023-1932 , EUVD-2023-2152

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
7.4%
EPSS 7.4% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

CasaOS is an open-source Personal Cloud system. Due to a lack of IP address verification an unauthenticated attackers can execute arbitrary commands as `root` on CasaOS instances. The problem was addressed by improving the detection of client IP addresses in `391dd7f`. This patch is part of CasaOS 0.4.4. Users should upgrade to CasaOS 0.4.4. If they can't, they should temporarily restrict access to CasaOS to untrusted users, for instance by not exposing it publicly.

Patch / fix

  • go github.com/IceWhaleTech/CasaOS-Gateway 0.4.4
  • icewhale casaos-gateway 0.4.4

Is CVE-2023-37265 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

7.36% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • sonarsource.com https://www.sonarsource.com/blog/security-vulnerabilities-in-casaos referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/IceWhaleTech/CasaOS-Gateway
<0.4.4
0.4.4

Affected products

  • IceWhaleTech CasaOS-Gateway
  • icewhale casaos-gateway

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality
  • CWE-348 Use of Less Trusted Source

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.