dbcve.org
AeroApplication · 63moons

CVE-2024-51557

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to 1.1.7 / 120820241550 or later.
See remediation →
71/100
Remediation priority · Elevated
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
This vulnerability exists in the Wave 2.0 due to missing rate limiting on OTP requests in an API endpoint. An authenticated remote attacker could exploit this vulnerability by sending multiple OTP request through vulnerable API endpoint which could lead to the OTP bombing/flooding on the targeted system.

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 · moderate confidence

This vulnerability exists in Wave 2.0 due to missing rate limiting on OTP requests in an API endpoint. An authenticated remote attacker can exploit this by sending multiple OTP requests through the vulnerable API, leading to OTP bombing/flooding on the targeted system.

MitigationImplement rate limiting on the OTP request API endpoint to restrict the number of OTP requests per user/IP within a defined time window, and consider adding CAPTCHA or account lockout mechanisms after failed attempts.

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
AeroApplication
Affected:< 120820241550
Wave 2.0Application
Affected:< 1.1.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 installed product and version
    Locate the 63moons Aero or Wave 2.0 installation and determine its version number. For Aero, check build version 120820241550 or later. For Wave 2.0, check version 1.1.7 or later.
    Affected if The installed version is below 120820241550 for Aero or below 1.1.7 for Wave 2.0
  2. Locate OTP API endpoint
    Identify the API endpoint that handles OTP (One-Time Password) requests in the Wave 2.0 application. Common patterns include endpoints under /api/otp, /api/auth/otp, or similar authentication-related paths.
    Affected if The OTP request API endpoint exists and is accessible without additional verification barriers
  3. Check if OTP endpoint accepts requests
    Send a test OTP request to the identified API endpoint using an authenticated session to verify the endpoint is functional and processing requests.
    Affected if The endpoint accepts OTP requests and processes them without requiring additional verification like CAPTCHA or proof-of-work
  4. Verify rate limiting configuration
    Inspect the web server or application configuration for rate limiting rules on OTP endpoints. Check for any throttling, request limits, or IP-based restrictions applied to the OTP API path.
    Affected if No rate limiting, request throttling, or IP-based restrictions are configured on the OTP endpoint

You are affected if you are running 63moons Aero before build 120820241550 or Wave 2.0 before version 1.1.7, and the OTP API endpoint is accessible and processes requests without rate limiting in place.

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 1.1.7 / 120820241550 or later
Fixed in 1.1.7120820241550
Interim mitigation

Implement rate limiting on the OTP request API endpoint to restrict the number of OTP requests per user/IP within a defined time window, and consider adding CAPTCHA or account lockout mechanisms after failed attempts.

Recommended fix Moderate confidence

Aero: 120820241550 | Wave 2.0: 1.1.7

  1. 1. Identify the affected product (Aero or Wave 2.0) currently deployed in your environment.
  2. 2. Determine the current version of the installed product.
  3. 3. For Aero users: Upgrade to version 120820241550 or later.
  4. 4. For Wave 2.0 users: Upgrade to version 1.1.7 or later.
  5. 5. After upgrading, verify that the rate limiting is now enforced on OTP request API endpoints.
  6. 6. Test the OTP functionality to ensure legitimate OTP requests still work correctly after the upgrade.

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

Fix this in Aero Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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