CVE-2021-34733
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 · uneditedA vulnerability in the CLI of Cisco Prime Infrastructure and Cisco Evolved Programmable Network (EPN) Manager could allow an authenticated, local attacker to access sensitive information stored on the underlying file system of an affected system. This vulnerability exists because sensitive information is not sufficiently secured when it is stored. An attacker could exploit this vulnerability by gaining unauthorized access to sensitive information on an affected system. A successful exploit could allow the attacker to create forged authentication requests and gain unauthorized access to the affected system.
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 confidenceA vulnerability in the CLI of Cisco Prime Infrastructure and Cisco EPN Manager allows authenticated local attackers to access sensitive information stored insecurely on the underlying file system. The sensitive data (likely credentials or authentication tokens) can be extracted and used to forge authentication requests, enabling unauthorized access to the affected system.
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< 5.0< 3.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Cisco productRun 'show version' or check the product name in the CLI/login screen to determine if this is Cisco Prime Infrastructure or Cisco Evolved Programmable Network ManagerAffected if The product is Cisco Prime Infrastructure or Cisco EPN Manager
-
Check the installed version against affected rangesRun 'show version' to display the installed software version. For Prime Infrastructure, compare to < 3.8. For EPN Manager, compare to < 5.0Affected if The version number is lower than 3.8 for Prime Infrastructure or lower than 5.0 for EPN Manager
-
Verify CLI access is enabledConfirm that local CLI access is available to the system via SSH, console, or direct terminal accessAffected if CLI access is available to authenticated local users
-
Check for insecurely stored sensitive filesInspect the file system for configuration files, credential stores, or authentication token files that may be stored with weak permissions or in plaintextAffected if Sensitive files containing credentials or tokens are found with overly permissive access controls or in unencrypted format
A system is affected if it runs Cisco Prime Infrastructure below version 3.8 or Cisco EPN Manager below version 5.0, has CLI access enabled, and contains sensitive credential or token files stored with weak file system permissions.
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.
dbcve · scoped3.85.0
Apply the vendor-supplied security patch from Cisco for this vulnerability. Prior to patching, restrict local CLI access to trusted administrators and implement monitoring for suspicious file system access patterns.
Cisco Prime Infrastructure 3.8+ or EPN Manager 5.0+
- 1. Identify which Cisco product is in use: Prime Infrastructure or Evolved Programmable Network (EPN) Manager
- 2. Determine current installed version via CLI or web interface
- 3. For Prime Infrastructure: Plan upgrade to version 3.8 or later
- 4. For Evolved Programmable Network Manager: Plan upgrade to version 5.0 or later
- 5. Review Cisco release notes for upgrade prerequisites and compatibility requirements
- 6. Perform full system backup including configuration and database
- 7. Execute upgrade following Cisco official upgrade documentation
- 8. Verify successful installation and validate that the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34733 — 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-34733 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