dbcve.org
LoxilbApplication

CVE-2024-53348

HIGH · 7.4 CVSS v3.1 Published 2025-03-21
Fix available
A fix is available. Upgrade to after 0.9.7 or later.
See remediation →
83/100
Remediation priority · High
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
LoxiLB v.0.9.7 and before is vulnerable to Incorrect Access Control which allows attackers to obtain sensitive information and escalate privileges.

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

LoxiLB versions 0.9.7 and before contain an Incorrect Access Control vulnerability that allows unauthenticated or unauthorized attackers to bypass access controls, obtain sensitive information, and escalate privileges to higher-level system access.

MitigationUpgrade to a fixed version of LoxiLB beyond 0.9.7 when available. Review access control configurations and audit user permissions until the patch can be applied.

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
LoxilbApplication
Affected:<= 0.9.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 LoxiLB version
    Run 'loxilb --version' or check the binary/package version installed on the system
    Affected if The installed version is 0.9.7 or any version lower than 0.9.7
  2. Confirm LoxiLB is running
    Check if the loxilb process or service is active on the system using 'ps aux | grep loxilb' or 'systemctl status loxilb'
    Affected if LoxiLB is running and the version is vulnerable (<= 0.9.7)
  3. Review access control configuration
    Inspect access control lists, authentication settings, or any configuration files that govern who can access LoxiLB services
    Affected if Access controls are present but may be bypassable due to the incorrect access control flaw
  4. Check for unauthenticated endpoints
    Survey exposed network interfaces and ports where LoxiLB is listening to determine if they permit unauthenticated access
    Affected if LoxiLB is accessible over network without authentication and version is <= 0.9.7

The environment is affected if LoxiLB version 0.9.7 or lower is installed and running, particularly if accessible over a network without proper authentication controls.

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
Upgrade available Upgrade to a release after 0.9.7
Interim mitigation

Upgrade to a fixed version of LoxiLB beyond 0.9.7 when available. Review access control configurations and audit user permissions until the patch can be applied.

Fix this in Loxilb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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