dbcve.org
Csaf Validator LibApplication · Csaf Validator Lib Project

CVE-2022-47924

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 0.1.0 or later.
See remediation →
65/100
Remediation priority · Elevated

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
An high privileged attacker may pass crafted arguments to the validate function of csaf-validator-lib of a locally installed Secvisogram in versions < 0.1.0 wich can result in arbitrary code execution and DoS once the users triggers the validation.

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

The csaf-validator-lib contains a vulnerability in its validate function where an attacker with high privileges can pass crafted arguments that lead to arbitrary code execution or denial of service. The vulnerability affects Secvisogram installations using csaf-validator-lib versions prior to 0.1.0.

MitigationUpgrade csaf-validator-lib to version 0.1.0 or later and review any custom validation logic for similar injection 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
Csaf Validator LibApplication
Affected:< 0.1.0

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

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 csaf-validator-lib is in use
    Search your codebase, dependencies, or package manager for 'csaf-validator-lib' or '@secvisogram/csaf-validator-lib'
    Affected if The library is present in dependencies or imported code
  2. Determine installed version of csaf-validator-lib
    Run package manager command to check installed version: npm list csaf-validator-lib, pip show csaf-validator-lib, or equivalent for your package manager
    Affected if Version is below 0.1.0 or version cannot be determined (library present but version unknown and likely old)
  3. Check if Secvisogram is deployed
    Search for Secvisogram installation or usage in your environment, check if your application integrates Secvisogram for CSAF validation
    Affected if Secvisogram is deployed and uses the vulnerable library
  4. Verify validate function is accessible to high-privilege users
    Review application access controls and determine if users with elevated privileges can invoke the validate function with custom arguments
    Affected if High-privilege users can pass arbitrary arguments to the validate function

You are affected if csaf-validator-lib version below 0.1.0 is installed as a dependency of Secvisogram or any application, and users with elevated privileges can invoke the validate function with custom arguments.

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 0.1.0 or later
Fixed in 0.1.0
Interim mitigation

Upgrade csaf-validator-lib to version 0.1.0 or later and review any custom validation logic for similar injection vectors.

Recommended fix Moderate confidence

0.1.0 or later

  1. 1. Identify the project dependency file (package.json, requirements.txt, or similar) that includes csaf-validator-lib
  2. 2. Locate the csaf-validator-lib dependency entry
  3. 3. Update the version constraint to specify version 0.1.0 or later (e.g., "csaf-validator-lib": ">=0.1.0" or "csaf-validator-lib": "latest")
  4. 4. Run the package manager update command (npm update, pip install -U, or equivalent) to fetch the fixed version
  5. 5. Verify the installed version is 0.1.0 or later using the package manager's version check command
  6. 6. Test the application to ensure validation functionality works correctly with the updated library

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

Fix this in Csaf Validator Lib Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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