CVE-2012-4947
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 · uneditedAgile FleetCommander and FleetCommander Kiosk before 4.08 store database credentials in cleartext, which allows remote attackers to obtain sensitive information via requests to unspecified pages.
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 confidenceAgile FleetCommander and FleetCommander Kiosk versions prior to 4.08 store database credentials in cleartext rather than using encryption or secure storage mechanisms. This allows remote attackers who can access certain unspecified web pages to retrieve these credentials through HTTP requests.
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<= 4.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
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Confirm FleetCommander installation and identify versionLocate the FleetCommander installation directory or running service, then check the application version (often displayed in an About page, in a version.txt file, or in the executable properties)Affected if The installed version is 4.0 or lower, or any version prior to 4.08 (such as 4.01 through 4.07) since the cleartext credential storage was not fixed until version 4.08
-
Determine if the web interface is network-accessibleAttempt to access the FleetCommander web interface from a non-localhost network location, or review firewall rules and network configurations to see if the web service port (commonly port 80/443) is exposed to untrusted networksAffected if The web interface is reachable from networks other than trusted local administration networks, increasing exposure to remote attackers
-
Locate database configuration filesSearch the FleetCommander installation directory for configuration files that contain database connection strings, typically files named config.ini, database.conf, db.config, or similarAffected if Database credentials (username and password) are stored in plain text within configuration files rather than being encrypted, hashed, or stored in a secure credential vault
-
Verify credential storage mechanismExamine the identified database configuration files to determine whether credentials appear as plaintext strings or are obfuscated, encrypted, or referenced from a secure storage mechanismAffected if Credentials are stored as clear, readable text strings that could be directly obtained by an attacker making HTTP requests to the web application
You are affected if FleetCommander or FleetCommander Kiosk version 4.07 or earlier is installed and the web interface is accessible, with database credentials stored in cleartext configuration files.
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 dataUpgrade to FleetCommander version 4.08 or later which addresses the cleartext credential storage. If immediate upgrade is not possible, restrict access to all web-facing pages and implement network segmentation to limit exposure.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4947 — 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-2012-4947 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