CVE-2012-4949
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 · uneditedSQL injection vulnerability in ESRI ArcGIS 10.1 allows remote authenticated users to execute arbitrary SQL commands via the where parameter to a query URI for a REST service.
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 confidenceSQL injection vulnerability in ESRI ArcGIS 10.1 REST service allows remote authenticated users to execute arbitrary SQL commands via the 'where' parameter in a query URI. The vulnerability exists in the REST query interface, enabling attackers with valid credentials to manipulate SQL queries.
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= 10.1CVSS 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 ArcGIS Server versionLocate the ArcGIS Server installation and check the exact version number. This can typically be found in the server's about or system info page, or by checking the installed software details.Affected if The installed version is exactly 10.1 (not patched or upgraded)
-
Verify REST services are enabledCheck if the ArcGIS REST services directory is accessible. This is typically available at /arcgis/rest/ on the server's web context.Affected if The REST endpoint is accessible and returns a service directory listing
-
Confirm REST services are network-exposedDetermine if the REST interface is reachable from network locations. Test by attempting to access the REST URL from an external system or reviewing firewall/network configuration.Affected if The REST services are exposed to untrusted networks or the internet
-
Check REST service authentication configurationReview the authentication settings for the REST query interface. Verify whether anonymous access is permitted or if proper authentication enforcement is configured.Affected if Authenticated access is not properly enforced, allowing unauthorized users to reach query endpoints
You are affected if ArcGIS Server version is exactly 10.1, the REST service is enabled and network-accessible, and the 'where' parameter in query URIs can be manipulated without proper sanitization or authentication controls.
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 vendor patch for ArcGIS 10.1 or upgrade to a supported version. Until patched, restrict network access to the REST service endpoints and enforce strict least-privilege authentication. Implement web application firewall rules to sanitize the 'where' parameter.
- 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-2012-4949 — 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-4949 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