CVE-2012-0147
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 · uneditedMicrosoft Forefront Unified Access Gateway (UAG) 2010 SP1 and SP1 Update 1 does not properly configure the default web site, which allows remote attackers to obtain sensitive information via a crafted HTTPS request, aka "Unfiltered Access to UAG Default Website Vulnerability."
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 confidenceMicrosoft Forefront Unified Access Gateway (UAG) 2010 SP1 and SP1 Update 1 contains an improper configuration of the default web site that allows unauthenticated remote attackers to obtain sensitive information through specially crafted HTTPS requests. The vulnerability stems from insufficient access controls on the default UAG website.
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= 2010CVSS 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 UAG 2010 installationCheck installed programs or services for Microsoft Forefront Unified Access Gateway 2010. Look for the UAG service and management console.Affected if UAG 2010 is installed on the system
-
Identify UAG version and service packCheck the installed version of Forefront UAG 2010, specifically looking for SP1 or SP1 Update 1. This can be found in Add/Remove Programs, the UAG console, or the registry under the UAG installation directory.Affected if Version is Forefront UAG 2010 with Service Pack 1 or Service Pack 1 Update 1
-
Locate default UAG website configurationCheck the IIS Manager or UAG configuration for the default website that UAG creates during installation. Identify the bindings and physical path of the default site.Affected if A default UAG website exists in IIS with default bindings
-
Review access control settings on default websiteExamine the authentication and authorization settings for the default UAG website in IIS. Check for anonymous access enabled and lack of IP/domain restrictions. Look for the presence of sensitive information accessible without authentication.Affected if Default website allows unauthenticated access and exposes sensitive configuration or internal information
-
Test for information disclosure via HTTPS requestsSend specially crafted HTTPS requests to the default website (e.g., accessing common internal paths, configuration files, or administrative endpoints) without credentials. Observe if sensitive information is returned.Affected if Unauthenticated requests to the default site return sensitive data such as configuration details, internal paths, or administrative information
If Forefront UAG 2010 SP1 or SP1 Update 1 is installed with its default website configured to allow unauthenticated access and expose sensitive information, the environment is affected by CVE-2012-0147.
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 Microsoft security update for CVE-2012-0147 and verify that the default web site is properly configured with appropriate access restrictions. Consider network-level filtering to limit exposure of the UAG default website to untrusted networks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0147 — 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-0147 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