dbcve.org
E Invoice Approval SystemApplication · Infodrom

CVE-2023-35067

HIGH · 7.5 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to 20230701 or later.
See remediation →
84/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
Plaintext Storage of a Password vulnerability in Infodrom Software E-Invoice Approval System allows Read Sensitive Strings Within an Executable. This issue affects E-Invoice Approval System: before v.20230701.

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 E-Invoice Approval System stores passwords in plaintext, likely hardcoded within the executable or stored in an insecure configuration file. An attacker who gains access to the application files or executable can extract these plaintext credentials, potentially gaining unauthorized access to the system or associated data.

MitigationUpdate to E-Invoice Approval System v.20230701 or later, which presumably implements proper credential handling. If unable to update immediately, change any exposed credentials and implement secure credential storage mechanisms.

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
E Invoice Approval SystemApplication
Affected:< 20230701

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed version of Infodrom E Invoice Approval System
    Locate the application executable or installation directory and check the file properties, version info, or any about/version dialog within the application
    Affected if The version is earlier than 20230701
  2. Locate and inspect configuration files
    Search the application installation directory for configuration files such as .ini, .xml, .json, .conf, .cfg, .config, or properties files
    Affected if Any configuration file contains plaintext passwords or credentials stored without encryption
  3. Search for hardcoded strings in the executable
    Use a string extraction tool or hex editor to examine the main executable for visible plaintext strings resembling passwords, credentials, or connection strings
    Affected if The executable contains plaintext passwords, hardcoded credentials, or password-like strings in cleartext
  4. Check for password or credential fields in config files
    Open and review all configuration files for fields such as 'password', 'pwd', 'pass', 'credential', or 'secret' and verify whether their values are stored in plaintext
    Affected if Credentials are stored in cleartext rather than being hashed, encrypted, or stored in a secure vault

A user is affected if the installed version is earlier than 20230701 AND plaintext passwords are found in configuration files or embedded in the executable.

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

Update to E-Invoice Approval System v.20230701 or later, which presumably implements proper credential handling. If unable to update immediately, change any exposed credentials and implement secure credential storage mechanisms.

Recommended fix Moderate confidence

version 20230701

  1. 1. Backup the current E-Invoice Approval System database and configuration files
  2. 2. Obtain the updated E-Invoice Approval System version 20230701 from Infodrom Software's official distribution channels
  3. 3. Review the vendor's upgrade documentation for version 20230701
  4. 4. Install the upgrade following the documented upgrade procedure
  5. 5. Verify that passwords are no longer stored in plaintext after the upgrade (e.g., check configuration files or database for hashed/encrypted passwords)
  6. 6. Test that the E-Invoice Approval System functions correctly post-upgrade

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

Fix this in E Invoice Approval System 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-2023-35067 — 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-35067 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