dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-6749

MEDIUM · 6.3 CVSS v3.1 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
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
Seth Fogie, member of the AXIS Camera Station Pro Bug Bounty Program, has found that the Incident report feature may expose sensitive credentials on the AXIS Camera Station windows client. If Incident report is not being used with credentials configured this flaw does not apply. Axis has released patched versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

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 Incident report feature in AXIS Camera Station Pro Windows client contains a vulnerability that exposes sensitive credentials. This occurs when the Incident report feature is configured with credentials for its operation. An attacker with local access or potentially through log files could obtain these exposed credentials.

MitigationUpdate AXIS Camera Station Pro to the patched versions released by Axis. Additionally, review and audit any systems where the Incident report feature was configured with credentials to determine if credential exposure may have occurred, and rotate exposed credentials as a precaution.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

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 AXIS Camera Station Pro installation and version
    Open Windows Control Panel or Settings > Apps & Features, locate AXIS Camera Station Pro, and note the installed version number. Compare this version against any released patch versions from Axis for this CVE.
    Affected if The installed version falls within the vulnerable version range prior to the patch.
  2. Determine if Incident report feature is configured
    Launch AXIS Camera Station Pro client, navigate to the Incident report settings or configuration area (typically found under Settings, Reports, or similar menu options), and check whether any credentials have been configured for the feature's operation.
    Affected if The Incident report feature has been configured with credentials for its operation, as this is the condition that enables credential exposure.
  3. Inspect log files for exposed credentials
    Locate and examine log files created by AXIS Camera Station Pro (typically found in the application data directory or logs folder). Search these files for any stored or logged credentials, authentication tokens, or sensitive credential strings that may have been inadvertently recorded.
    Affected if Log files contain plaintext credentials or sensitive authentication data associated with the Incident report feature configuration.
  4. Check for credential storage locations
    Examine the application configuration files or database where AXIS Camera Station Pro stores settings, particularly looking for stored credentials related to incident reporting, email notifications, or external integrations.
    Affected if Credentials are found stored in plaintext or with weak encryption in configuration files accessible to local users.

A user is affected if they have an unpatched version of AXIS Camera Station Pro with the Incident report feature configured using credentials, or if credentials appear in accessible log or configuration files.

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

Update AXIS Camera Station Pro to the patched versions released by Axis. Additionally, review and audit any systems where the Incident report feature was configured with credentials to determine if credential exposure may have occurred, and rotate exposed credentials as a precaution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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