dbcve.org
Aim StarApplication · Reedos

CVE-2024-45787

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Reedos aiM-Star version 2.0.1 due to transmission of sensitive information in plain text in certain API endpoints. An authenticated remote attacker could exploit this vulnerability by manipulating a parameter through API request URL and intercepting response of the API request leading to exposure of sensitive information belonging to other users.

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 in Reedos aiM-Star v2.0.1 involves API endpoints transmitting sensitive information in plain text without encryption. An authenticated attacker can manipulate parameters in API request URLs and intercept responses to access sensitive data belonging to other users, indicating a potential Insecure Direct Object Reference (IDOR) issue combined with unencrypted data transmission.

MitigationImplement TLS/SSL encryption for all API endpoint communications and add proper authorization validation to ensure users can only access their own data, preventing horizontal privilege escalation through parameter manipulation.

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
Aim StarApplication
Affected:= 2.0.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify the installed aiM-Star version
    Check the application version in the software's about page, installation directory, or by querying the API server headers. Common paths include looking at the login page footer, a /api/version endpoint, or the installer metadata.
    Affected if The installed version is exactly 2.0.1 (this specific version is affected)
  2. Confirm API endpoints are accessible over HTTP
    Attempt to access known API endpoints using http:// rather than https://. Use a browser or curl command to test if the API responds on port 80/8080 without redirect to HTTPS.
    Affected if API endpoints respond over unencrypted HTTP (port 80/8080) without enforcing TLS/SSL, allowing traffic interception
  3. Verify API authentication is enabled
    Test API endpoints without providing credentials. Check if requests to endpoints like /api/users, /api/data, or /api/records require valid authentication tokens/sessions.
    Affected if The system uses API authentication (required for the authenticated attacker scenario) and allows parameter manipulation in requests
  4. Check for predictable object references in API URLs
    Review API endpoint URL structures for parameter-based access to data objects (e.g., /api/user/123, /api/record?id=456). Attempt to modify numeric or sequential parameters to access other users' data.
    Affected if API URLs contain directly referenceable object parameters (like user IDs, record IDs) that can be manipulated to access other users' data without proper authorization checks

A user is affected if they have aiM-Star version 2.0.1 deployed and its API endpoints are accessible over unencrypted HTTP with authenticated access that fails to enforce proper authorization between users on parameter-based data 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement TLS/SSL encryption for all API endpoint communications and add proper authorization validation to ensure users can only access their own data, preventing horizontal privilege escalation through parameter manipulation.

Fix this in Aim Star Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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