Application Policy Infrastructure Controller Enterprise ModulePlugin / extension · Cisco
CVE-2018-0368
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 Cisco Digital Network Architecture (DNA) Center could allow an authenticated, local attacker to access sensitive information on an affected system. The vulnerability is due to insufficient security restrictions imposed by the affected software. An attacker could exploit this vulnerability by accessing unprotected log files. A successful exploit could allow the attacker to access sensitive log files, which may include system credentials, on the affected device. Cisco Bug IDs: CSCvi22400.
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 confidenceCisco DNA Center contains a local file exposure vulnerability where insufficient security restrictions on log files allow an authenticated local attacker to access unprotected log files. The vulnerability exposes sensitive information including system credentials stored in log files. An attacker with local access and valid credentials can exploit this by directly accessing log files that lack proper access controls.
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
Application Policy Infrastructure Controller Enterprise ModulePlugin / extension
= 1.1_baseCVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product versionCheck the Cisco Application Policy Infrastructure Controller Enterprise Module version installed in your environment. This is typically viewable through the Cisco DNA Center administrative interface or via CLI with 'show version' command.Affected if Version is 1.1_base - this is the specific affected version per the CVE advisory.
-
Locate log files on the systemIdentify where log files are stored on the Cisco DNA Center appliance. Log files may be located in standard system log directories or application-specific log folders.Affected if Log files exist on the system - the vulnerability affects systems with any log files present.
-
Inspect file permissions on log filesCheck the file system permissions on identified log files using appropriate file permission inspection methods (e.g., 'ls -la' command on log directories). Look for world-readable or group-readable permissions.Affected if Log files have permissions that allow access by users other than the intended owner or administrative group - the vulnerability requires insufficient access restrictions.
-
Search for credential patterns in logsExamine log file contents for exposed credentials, API keys, passwords, or authentication tokens. Use grep or similar tools to search for patterns like 'password', 'credential', 'token', or 'key' in log files.Affected if Log files contain readable sensitive information such as stored system credentials - this confirms exploitation of the vulnerability.
You are affected if your Cisco Application Policy Infrastructure Controller Enterprise Module is version 1.1_base AND log files on the system have overly permissive file access controls that could allow an authenticated local user to read sensitive credential information.
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 dataApply the Cisco patch for CSCvi22400 and ensure log files are stored with restricted file permissions. Consider implementing log rotation with secure permissions and review logs for exposed credentials to rotate any compromised credentials.
Fix this in Application Policy Infrastructure Controller Enterprise Module
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0368 — 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-2018-0368 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