CVE-2017-3067
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 · uneditedAdobe Experience Manager Forms versions 6.2, 6.1, 6.0 have an information disclosure vulnerability resulting from abuse of the pre-population service in AEM Forms.
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 confidenceAdobe Experience Manager Forms versions 6.0, 6.1, and 6.2 contain an information disclosure vulnerability in the pre-population service. The pre-population service, designed to pre-fill form fields with data, can be abused to access sensitive information that should not be exposed. This represents a confidentiality impact resulting from improper access controls on the service.
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.0= 6.1= 6.2CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Verify AEM Forms versionAccess the Adobe Experience Manager system information page (typically at /system/console/bundles or check the product version through the AEM welcome page) and determine the exact Forms version installed.Affected if The installed version is 6.0, 6.1, or 6.2 exactly as listed in the affected versions.
-
Identify pre-population service endpointLocate the Forms pre-population service configuration in AEM. This is typically found in the AEM Forms configuration settings or through the OSGi service console under the Forms workflow services.Affected if The pre-population service component exists and is enabled in the AEM Forms installation.
-
Test service accessibility without authenticationAttempt to access the pre-population service endpoint directly (commonly via Forms services or data services) using an unauthenticated request or a low-privilege user account to determine if sensitive data can be retrieved.Affected if The pre-population service returns form data, personal information, or sensitive content without requiring proper authorization credentials.
-
Review access control configurationExamine the AEM Forms permission settings and ACLs (Access Control Lists) configured for the pre-population service through the AEM user management or group permissions console.Affected if The access control configuration permits unauthenticated or unauthorized users to retrieve data through the pre-population service.
A user is affected if AEM Forms version 6.0, 6.1, or 6.2 is installed AND the pre-population service is accessible without proper authentication, allowing unauthorized data retrieval.
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 AEM Forms to a patched version (6.3 or later) and review access controls on the pre-population service to ensure proper authorization is enforced for data retrieval operations.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3067 — 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-2017-3067 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