CVE-2013-3512
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 · uneditedThe Cacti component in GroundWork Monitor Enterprise 6.7.0 does not properly perform authorization checks, which allows remote authenticated users to read or modify configuration settings via unspecified vectors, as demonstrated by reading credentials.
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 confidenceGroundWork Monitor Enterprise 6.7.0 includes a Cacti component that fails to properly enforce authorization checks on certain operations. This allows any authenticated user (regardless of privilege level) to read sensitive configuration settings, including stored credentials, and potentially modify those configurations. The vulnerability stems from missing or insufficient access control logic within the Cacti integration.
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= 6.7.0CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Confirm GroundWork Monitor versionCheck the installed version of GroundWork Monitor Enterprise. Look for version files in the installation directory, check the web interface about page, or run: grep -r '6.7.0' /usr/local/groundwork or similar installation paths.Affected if Version is exactly 6.7.0 - this is the only affected version listed.
-
Verify Cacti component is presentCheck for Cacti integration in the GroundWork installation. Look for Cacti directories, scripts, or web paths such as /cacti/, /groundwork/cacti/, or examine the GroundWork configuration files for Cacti-related settings.Affected if Cacti component exists within the GroundWork installation - the vulnerability is in this specific component.
-
Check Cacti authorization configurationExamine Cacti's config.php or database settings for authenication and authorization settings. Look for: $config["auth_enabled"], $config["auth_method"], and user permission tables in the Cacti database.Affected if Authorization is not properly enforced on Cacti configuration operations - the flaw allows any authenticated user to access sensitive settings.
-
Inspect credential storage accessibilityReview file permissions on Cacti configuration files that may contain credentials (typically config_database.php or similar). Check if non-admin authenticated users can read these files via the web interface or API.Affected if Stored credentials in Cacti config are readable by any authenticated user regardless of privilege level.
You are affected if running GroundWork Monitor Enterprise 6.7.0 with the Cacti component integrated and the Cacti authorization does not restrict low-privilege users from reading sensitive configuration data including stored credentials.
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 dataImplement role-based access control (RBAC) and proper authorization validation for all configuration-related operations in the Cacti component. Restrict credential access to only privileged administrators and validate user permissions before allowing read/write operations on configuration data.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3512 — 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-2013-3512 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