CVE-2021-3130
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 · uneditedWithin the Open-AudIT up to version 3.5.3 application, the web interface hides SSH secrets, Windows passwords, and SNMP strings from users using HTML 'password field' obfuscation. By using Developer tools or similar, it is possible to change the obfuscation so that the credentials are visible.
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 confidenceIn Open-AudIT up to version 3.5.3, SSH secrets, Windows passwords, and SNMP strings are displayed in the web interface using HTML password fields for visual obfuscation only. The actual credential values are present in the page source and can be trivially revealed by modifying the HTML input type from 'password' to 'text' via browser developer tools, enabling unauthorized credential disclosure.
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<= 4.0.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed Open-AudIT versionAccess the Open-AudIT web interface and navigate to the admin or about section, or run 'omk version' if you have CLI access. Compare the version number to the affected range: <= 4.0.2.Affected if The installed version is 4.0.2 or lower.
-
Navigate to the credentials management pageLog into the Open-AudIT web interface and locate the section where credentials are managed (typically under Admin, Credentials, or Devices > Credentials).Affected if You can access a credentials listing or detail page in the interface.
-
Inspect the credential display fieldsIn the web browser, view the page source (right-click > View Page Source or press Ctrl+U) and search for 'type="password"' or the credential field names. Check if actual plaintext values are present in the value attributes.Affected if The page source contains plaintext SSH secrets, Windows passwords, or SNMP community strings in the HTML.
-
Test HTML input type modificationIn the browser developer tools (F12), locate a password field displaying a credential, change the input type attribute from 'password' to 'text', and observe whether the actual credential value becomes visible.Affected if Changing type="password" to type="text" reveals the plaintext credential value.
You are affected if running Open-AudIT version 4.0.2 or lower AND the credentials page displays credentials that can be revealed by inspecting the HTML source or modifying the input type from password to text.
Generated from the published advisory. Verify against your own configuration.
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 dataModify the application to never transmit actual credential values to the client browser; instead, store and display only salted hashes or masked placeholders (e.g., '********') while performing credential verification server-side.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-3130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-3130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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