dbcve.org
ScrutiswebApplication · Iagona

CVE-2023-35763

MEDIUM · 5.5 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to after 2.1.37 or later.
See remediation →
57/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
Iagona ScrutisWeb versions 2.1.37 and prior are vulnerable to a cryptographic vulnerability that could allow an unauthenticated user to decrypt encrypted passwords into plaintext.

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

Iagona ScrutisWeb versions 2.1.37 and prior contains a cryptographic vulnerability allowing unauthenticated users to decrypt encrypted passwords to plaintext, likely due to weak encryption algorithm, hardcoded keys, or improper key management.

MitigationUpgrade to a version that addresses the cryptographic vulnerability, or implement strong password hashing (e.g., bcrypt, Argon2) with proper salt generation and secure key management if no patch is available.

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
ScrutiswebApplication
Affected:<= 2.1.37

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm ScrutisWeb installation and version
    Locate the ScrutisWeb application directory and check the version information (typically found in application metadata, about page, or version file)
    Affected if Version is 2.1.37 or lower
  2. Identify password storage location
    Search for configuration files, databases, or credential stores where ScrutisWeb stores user passwords
    Affected if Encrypted passwords are found stored in plaintext-equivalent format
  3. Locate encryption key material
    Inspect configuration files, source code, or application properties for hardcoded encryption keys or weak key management
    Affected if Hardcoded keys, static IVs, or weak key derivation is found in configuration or code
  4. Test password decryption capability
    Attempt to decrypt a known encrypted password using the identified key/algorithm to verify vulnerability
    Affected if Encrypted passwords can be decrypted to plaintext using recovered key material
  5. Verify encryption algorithm strength
    Examine the encryption mechanism used for password storage
    Affected if Weak algorithms (e.g., DES, weak AES modes, XOR) or no proper salting is used

The environment is affected if ScrutisWeb version 2.1.37 or lower is running AND hardcoded encryption keys or weak encryption is used for password storage, allowing unauthenticated password decryption.

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 a release after 2.1.37
Interim mitigation

Upgrade to a version that addresses the cryptographic vulnerability, or implement strong password hashing (e.g., bcrypt, Argon2) with proper salt generation and secure key management if no patch is available.

Recommended fix Moderate confidence

Version 2.1.38 or later (any release above 2.1.37)

  1. 1. Identify the current installed version of Iagona ScrutisWeb
  2. 2. Check Iagona's official release notes or support channels for version 2.1.38 or later
  3. 3. Download the latest stable version from the official vendor source
  4. 4. Back up the current installation and configuration files
  5. 5. Stop the ScrutisWeb service
  6. 6. Install the upgraded version following vendor documentation
  7. 7. Verify the hard-coded credentials vulnerability is resolved
  8. 8. Restart the service and confirm normal operation
Caveat Review release notes for any configuration or migration requirements between versions

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

Fix this in Scrutisweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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