dbcve.org
RathenaApplication

CVE-2025-58447

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2025-09-06 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
rAthena is an open-source cross-platform massively multiplayer online role playing game (MMORPG) server. Versions prior to commit 2f5248b have a heap-based buffer overflow in the login server, remote attacker to overwrite adjacent session fields by sending a crafted `CA_SSO_LOGIN_REQ` with an oversized token length. This leads to immediate denial of service (crash) and it is possible to achieve remote code execution via heap corruption. Commit 2f5248b fixes the issue.

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 heap-based buffer overflow vulnerability exists in the rAthena login server where a remote attacker can send a crafted CA_SSO_LOGIN_REQ packet containing an oversized token length. This allows adjacent session field overwriting, leading to immediate denial of service via crash and potential remote code execution through heap corruption.

MitigationUpgrade to the version containing commit 2f5248b which implements proper bounds checking on the token length field in the SSO login request handler.

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
RathenaApplication
Affected:< 2025-09-06

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 if rAthena login server is running
    Check for running processes named 'login-server', 'athena', or connections on typical login server ports (6900, 6121). Use: ps aux | grep -E '(login|athena|rathena)' or netstat -tlnp | grep -E '(6900|6121)'
    Affected if The login server process is running and exposed to network traffic
  2. Determine the installed rAthena version
    Check the source code version or binary build date. Look for a version file in the rAthena installation directory, or check the git commit hash with: git -C /path/to/rathena log -1 --format='%H %ci'
    Affected if The version or commit date is before 2025-09-06, or the commit hash does not include 2f5248b
  3. Verify if SSO login feature is enabled
    Examine the login server configuration file (typically login_conf.yml or login.conf) for 'sso_enable', 'enable_sso', or similar SSO-related settings. Also check if the login server is configured to accept CA_SSO_LOGIN_REQ packets.
    Affected if SSO login functionality is enabled in the login server configuration
  4. Check for the bounds checking fix in source code
    In the SSO login request handler source file (typically in src/login directory), search for the token length validation. Look for bounds checking code near the CA_SSO_LOGIN_REQ handler. Use: grep -n 'token.*length' src/login/*.cpp or manually inspect the SSO login handler function.
    Affected if The source code lacks proper bounds checking on the token length field, or the fix commit 2f5248b is not present

The environment is affected if the rAthena login server is running with SSO enabled and the version/commit predates the 2025-09-06 fix containing commit 2f5248b with proper token length bounds checking.

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 2025-09-06 or later
Fixed in 2025-09-06
Vendor patch github.com →
Interim mitigation

Upgrade to the version containing commit 2f5248b which implements proper bounds checking on the token length field in the SSO login request handler.

Recommended fix High confidence

Any rAthena build dated 2025-09-06 or later (commit 2f5248b9cd9a8c6b42422ddecfc4cc2cd0e69e4b and beyond)

  1. 1. Navigate to the rAthena server installation directory
  2. 2. Backup your current configuration files and database
  3. 3. Fetch the latest changes from the rAthena GitHub repository using: git fetch origin
  4. 4. Check the current commit to verify you have the fix: git log -1 --oneline
  5. 5. If not on commit 2f5248b or later, update to the latest version: git pull origin <branch> (where <branch> is your stable branch, commonly 'master' or 'stable')
  6. 6. Rebuild the login server component: cd src/login && make clean && make
  7. 7. Restart the login server to apply the patched binary
  8. 8. Verify the server is running without crashes
Caveat Review release notes for any database schema changes or configuration file updates between your current version and the latest version before upgrading

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

Fix this in Rathena Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing5.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,610
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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