dbcve.org
Axis OsOperating system · Axis

CVE-2025-0361

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 11.11.141 / 12.3.56 or later.
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
During an annual penetration test conducted on behalf of Axis Communications, Truesec discovered a flaw in the VAPIX Device Configuration framework that allowed for unauthenticated username enumeration through the VAPIX Device Configuration SSH Management API.

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 vulnerability allows unauthenticated attackers to enumerate valid usernames through the VAPIX Device Configuration SSH Management API in Axis Communications devices. This information disclosure flaw could facilitate brute-force or credential-stuffing attacks by enabling attackers to discover valid user accounts before attempting password attacks.

MitigationImplement proper authentication enforcement and rate limiting on the SSH Management API to prevent unauthenticated username enumeration. Consider returning consistent responses for both valid and invalid usernames to eliminate enumeration vectors.

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
Axis OsOperating system
Affected:>= 11.11.0, < 12.3.56
Axis Os 2024Operating system
Affected:< 11.11.141

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 the Axis OS version
    Access the device web interface or use the VAPIX API to query the system information (e.g., GET /axis-cgi/basicdeviceinfo.cgi) and retrieve the firmware/OS version field
    Affected if The installed version is >= 11.11.0 and < 12.3.56, or any version < 11.11.141 for the 2024 release branch
  2. Confirm the device is an Axis product
    Verify the device is an Axis Communications product by checking the manufacturer field in the device info or identifying the Axis branding in the web interface
    Affected if The device is not an Axis Communications device (this CVE only applies to Axis products)
  3. Determine if SSH Management API is exposed
    Check if the VAPIX SSH Management endpoint (typically /axis-cgi/sshmanagement.cgi) is reachable over the network from an unauthenticated perspective
    Affected if The SSH Management API endpoint is accessible without authentication
  4. Test for username enumeration behavior
    Send unauthenticated requests to the SSH Management API with different usernames and observe whether the response differs between valid and invalid usernames (e.g., different error messages, response codes, or timing)
    Affected if The API returns distinguishable responses that reveal whether a username exists in the system

The environment is affected if it is an Axis device running Axis OS versions 11.11.0 through 12.3.56 (or < 11.11.141 for 2024 branch) with an accessible SSH Management API that exposes username enumeration.

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 11.11.141 / 12.3.56 or later
Fixed in 11.11.14112.3.56
Interim mitigation

Implement proper authentication enforcement and rate limiting on the SSH Management API to prevent unauthenticated username enumeration. Consider returning consistent responses for both valid and invalid usernames to eliminate enumeration vectors.

Recommended fix Moderate confidence

Axis OS 12.3.56 (or later) or Axis OS 2024 11.11.141 (or later)

  1. 1. Identify the current Axis OS version running on the affected device
  2. 2. Determine which Axis OS branch the device is running (main release or 2024 release)
  3. 3. For devices on Axis OS 2024: Upgrade to version 11.11.141 or later
  4. 4. For devices on main Axis OS (11.11.0+): Upgrade to version 12.3.56 or later
  5. 5. After upgrade, verify the VAPIX Device Configuration SSH Management API no longer returns distinct responses for valid vs invalid usernames
  6. 6. Confirm the fix by reviewing Axis security advisories for CVE-2025-0361
Caveat Review Axis release notes for breaking changes between current version and target upgrade version before deploying

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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