dbcve.org
CasaApplication · Rakuten

CVE-2022-28704

HIGH · 7.2 CVSS v3.1 Published 2022-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Improper access control vulnerability in Rakuten Casa version AP_F_V1_4_1 or AP_F_V2_0_0 allows a remote attacker to log in with the root privilege and perform an arbitrary operation if the product is in its default settings in which is set to accept SSH connections from the WAN side, and is also connected to the Internet with the authentication information unchanged from the default settings.

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

Improper access control in Rakuten Casa versions AP_F_V1_4_1 and AP_F_V2_0_0 allows remote attackers to gain root SSH access when the device's SSH service is exposed to the WAN and default authentication credentials remain unchanged. An attacker with network access can execute arbitrary operations with root privileges.

MitigationChange default credentials immediately and disable or restrict SSH access to trusted networks only (not exposed to WAN). Verify no default credentials are in use and review firewall rules.

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
CasaApplication
Affected:= ap_f_v1_4_1= ap_f_v2_0_0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 Rakuten Casa firmware version
    Access the device administrative interface or check system information to determine the exact firmware version running on the Rakuten Casa device. Look for version indicators labeled as AP_F_V1_4_1 or AP_F_V2_0_0.
    Affected if The device is running firmware version AP_F_V1_4_1 or AP_F_V2_0_0 specifically.
  2. Determine SSH service exposure to WAN
    Review the device network configuration and firewall settings to confirm whether the SSH service port (default port 22) is accessible from external/WAN networks. Check port forwarding rules, ACLs, or firewall policies that allow inbound SSH connections from the internet.
    Affected if SSH service is enabled and exposed directly to the WAN/internet without network restrictions.
  3. Verify authentication credential status
    Check whether the default administrative credentials for the Rakuten Casa device have been changed from the manufacturer defaults. Attempt to authenticate with known default credentials or review authentication configuration to confirm custom passwords are in use.
    Affected if Default credentials remain unchanged or the device still accepts factory-default username/password combinations for SSH access.

The device is affected only if it runs firmware version AP_F_V1_4_1 or AP_F_V2_0_0 AND has SSH exposed to the WAN AND uses unchanged default credentials, allowing remote root SSH access.

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

Change default credentials immediately and disable or restrict SSH access to trusted networks only (not exposed to WAN). Verify no default credentials are in use and review firewall rules.

Recommended fix Moderate confidence
  1. 1. Access the Rakuten Casa admin interface or console.
  2. 2. Disable SSH access from the WAN side (change SSH access to LAN-only or trusted networks only).
  3. 3. Change the default authentication credentials (root password) to a strong, unique password.
  4. 4. If SSH access is not required from external networks, disable SSH service entirely or restrict it to localhost only.
  5. 5. Verify the configuration changes are applied and test that WAN SSH access is no longer possible.
  6. 6. Monitor logs for any unauthorized access attempts.

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

Fix this in Casa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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