Incorrect AuthorizationWeakness · CWE-863

CVE-2025-54554

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
tiaudit in Tera Insights tiCrypt before 2025-07-17 allows unauthenticated REST API requests that reveal sensitive information about the underlying SQL queries and database structure.

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

The tiaudit component in Tera Insights tiCrypt contains an unauthenticated REST API endpoint that exposes sensitive system information. Attackers can send requests without authentication to retrieve details about underlying SQL queries and database structure, which can aid in further attacks such as SQL injection or database enumeration.

MitigationRestrict tiaudit REST API endpoints to require valid authentication and authorization. Implement proper access controls and ensure error responses do not leak SQL query details or database schema information.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify if tiCrypt with tiaudit component is installed
    Check for the presence of tiCrypt installation directories or running processes related to tiaudit. Look for process names containing 'tiaudit' or 'tiCrypt' in running processes.
    Affected if The tiaudit component of tiCrypt is present and running in the environment.
  2. Locate tiaudit REST API endpoint configuration
    Examine tiCrypt configuration files for REST API endpoint definitions, typically in config files under the tiCrypt installation directory or /etc/tiCrypt/. Look for routes or endpoints defined for the tiaudit module.
    Affected if REST API endpoints for tiaudit are defined and enabled in the configuration.
  3. Test unauthenticated access to tiaudit endpoints
    Send an HTTP request to common tiaudit API paths such as /api/tiaudit/* or /tiaudit/api/* without providing any authentication credentials. Use curl or similar tool to inspect the HTTP response code and content.
    Affected if The endpoint returns HTTP 200 with system, SQL, or database information without requiring authentication.
  4. Verify if SQL query or database structure details are exposed
    Inspect responses from tiaudit endpoints for keywords like 'SELECT', 'INSERT', 'UPDATE', 'DELETE', table names, column names, database schema, or SQL error messages that reveal query details.
    Affected if Responses contain SQL query text, database schema information, or internal system details that should not be publicly accessible.
  5. Check access control configuration for tiaudit endpoints
    Review tiCrypt authentication and authorization configuration files to determine whether tiaudit endpoints are explicitly excluded from authentication requirements or have misconfigured access controls.
    Affected if The configuration shows tiaudit endpoints are marked as public, require no authentication, or have overly permissive access rules.

A user is affected if the tiaudit component is running and its REST API endpoints are accessible without authentication, returning sensitive SQL or database structure information.

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

Restrict tiaudit REST API endpoints to require valid authentication and authorization. Implement proper access controls and ensure error responses do not leak SQL query details or database schema information.

Have this fixed 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 help mitigating

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-2025-54554 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-54554 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