{"id":"acebb836-b601-4de6-85ce-755601ad0046","engagementId":"8a4b0d7b-d9bb-4008-b5d9-5a43a9886285","data":{"brief":{"id":"2a36e00f-0ccb-42e0-84ba-a3678696312c","name":"Millennium Challenge Corporation: Vulnerability Disclosure Program","tagline":"Report MCC Vulnerabilities! ","description":"\u003ch2\u003eIntroduction\u003c/h2\u003e\n\n\u003cp\u003eThe Millennium Challenge Corporation (“MCC”) is committed to ensuring the security of the American public by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.\u003c/p\u003e\n\n\u003cp\u003eThis policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.\u003c/p\u003e\n\n\u003cp\u003eWe encourage you to contact us to report potential vulnerabilities in our systems.\u003c/p\u003e\n\n\u003cp\u003eFor reports submitted in compliance with this policy, the MCC will acknowledge receipt within ten (ten) business days, endeavor to timely validate submissions, implement corrective actions if appropriate, and inform researchers of the disposition of reported vulnerabilities.\u003c/p\u003e\n\n\u003ch2\u003eAuthorization\u003c/h2\u003e\n\n\u003cp\u003eIf you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and MCC will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.\u003c/p\u003e\n\n\u003ch2\u003eGuidelines\u003c/h2\u003e\n\n\u003cp\u003eUnder this policy, “research” means activities in which you:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eNotify us as soon as possible after you discover a real or potential security issue.\u003c/li\u003e\n\u003cli\u003eMake every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.\u003c/li\u003e\n\u003cli\u003eOnly use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.\u003c/li\u003e\n\u003cli\u003eProvide us a reasonable amount of time to resolve the issue before you disclose it publicly.\u003c/li\u003e\n\u003cli\u003eDo not submit a high volume of low-quality reports.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eOnce you have established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone outside of your organization, or publicly until you follow the ‘Disclosure’ section below.\u003c/p\u003e\n\n\u003ch2\u003eTest Methods\u003c/h2\u003e\n\n\u003cp\u003eThe following test methods are not authorized:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eTest any system other than the systems set forth in the ‘Scope’ section below.\u003c/li\u003e\n\u003cli\u003eDisclose vulnerability information except as set forth in the ‘Reporting a Vulnerability’ and ‘Disclosure’ sections below.\u003c/li\u003e\n\u003cli\u003eEngage in physical testing of facilities or resources.\u003c/li\u003e\n\u003cli\u003eEngage in social engineering.\u003c/li\u003e\n\u003cli\u003eSend unsolicited electronic mail to MCC users, including “phishing” messages.\u003c/li\u003e\n\u003cli\u003eExecute or attempt to execute a denial of service (DoS) attack, a distributed denial of service (DDoS) attack, attempt any type of resource exhaustion attack on MCC networks or systems. Intentionally or unintentionally impair, disrupt, or disable MCC networks or systems, or test in a manner which could degrade the operation of MCC networks or systems.\u003c/li\u003e\n\u003cli\u003eIntroduce malicious software.\u003c/li\u003e\n\u003cli\u003eTest third-party applications, websites, or services that integrate with or link to or from MCC systems.\u003c/li\u003e\n\u003cli\u003eDelete, alter, share, retain, or destroy MCC data, or render MCC data inaccessible, or, use an exploit to exfiltrate data, establish command line access, establish a persistent presence on MCC systems, or “pivot” to other MCC systems.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eSecurity researchers may:\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eView or store MCC nonpublic data only to the extent necessary to document the presence of a potential vulnerability.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eSecurity researchers must:\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003ecease testing and notify us immediately upon discovery of a vulnerability,\u003c/li\u003e\n\u003cli\u003ecease testing and notify us immediately upon discovery of an exposure of nonpublic data, and,\u003c/li\u003e\n\u003cli\u003epurge any stored MCC nonpublic data upon reporting a vulnerability\u003c/li\u003e\n\u003c/ul\u003e","industryTagId":null,"targetsOverview":"\u003cp\u003eAny services not explicitly listed above are excluded from scope. Additionally, vulnerabilities found in non-federal systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to its disclosure policy (if any).\u003c/p\u003e\n\n\u003ch2\u003eReporting a Vulnerability\u003c/h2\u003e\n\n\u003cp\u003eReports should provide a detailed technical description of the steps required to reproduce the vulnerability, including a description of any tools needed to identify or exploit the vulnerability. Images (e.g., screen captures), and other documents may be attached to reports. It is helpful to give attachments illustrative names. Reports may include proof-of-concept code that demonstrates exploitation of the vulnerability. We request that any scripts or exploit code be embedded into non-executable file types. We can process all common file types and file archives; including, zip, 7zip, and gzip.\u003c/p\u003e\n\n\u003cp\u003eResearchers may submit reports anonymously or provide contact information in any preferred method or time of day they see fit to communicate. We may contact researchers to clarify reported vulnerability information or other technical interchange.\u003c/p\u003e\n\n\u003cp\u003eBy submitting a report to the MCC, researchers warrant that the report and any attachments do not violate the intellectual property rights of any third party and the submitter grants the MCC a non-exclusive, royalty-free, world-wide, perpetual license to use, reproduce, create derivative works, and publish the report and any attachments.\u003c/p\u003e\n\n\u003cp\u003eMCC will provide no monetary award, intention to advertise or give public credit to Researchers for identification of vulnerabilities.\u003c/p\u003e\n\n\u003ch2\u003eDisclosure\u003c/h2\u003e\n\n\u003cp\u003eThe MCC is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability in absence of a readily available corrective action likely increases versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 90 calendar days after you have received our acknowledgement of receipt of your report, or until you receive notice that MCC has remediated the vulnerability, whichever comes first. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us.\u003c/p\u003e\n\n\u003cp\u003eWe may share vulnerability reports with the Cybersecurity and Infrastructure Security Agency (CISA), other U.S. Government agencies, and vendors. We will not share names or contact data of security researchers, unless given explicit permission, or required by law or regulation.\u003c/p\u003e\n\n\u003ch2\u003eQuestions\u003c/h2\u003e\n\n\u003cp\u003eQuestions regarding this policy may be sent to vulnerabilitydisclosure@mcc.gov. The MCC encourages security researchers to contact us for clarification on any element of this policy. Please contact us prior to conducting research if you are unsure if a specific test method is inconsistent with or unaddressed by this policy. We also invite security researchers to contact us with suggestions for improving this policy.\u003c/p\u003e\n\n\u003cp\u003e\u003cem\u003eIf at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via support@bugcrowd.com before going any further.\u003c/em\u003e\u003c/p\u003e\n\n\u003chr\u003e\n\n\u003cp\u003eThe Cybersecurity and Infrastructure Security Agency (CISA) Vulnerability Disclosure Policy Platform (VDP Platform) gives agencies the option to use a centrally managed system to intake vulnerability information from and collaborate with the public to improve the security of their internet-accessible systems. CISA has a contract with EnDyna and Bugcrowd, private companies, to manage the platform used by the public to report vulnerability information; CISA exercises general oversight of the program.  CISA does not collect, maintain, use, or disseminate any Personally Identifiable Information (PII) provided to Bugcrowd for the purposes of creating a profile on the website or reporting a vulnerability to agencies other than CISA.  Participating agencies provide their own program vulnerability disclosure policy, setting out the agency’s parameters for vulnerability disclosures, including provisions for collection and use of submitted information. Any submissions of vulnerabilities pertaining to CISA’s own information systems would be governed by the DHS VDP brief.\u003c/p\u003e","safeHarborStatus":{"status":"full","label":"Safe harbor","description":"This engagement is fully committed to providing safe harbor for good-faith security research."},"collaborationEnabled":false,"additionalInformation":""},"scope":[{"id":"910ab574-7493-4ef5-9d34-c03174201674","name":"In Scope","targets":[{"id":"1a8df6ef-80fd-4ec8-9569-a45f5f2f8f43","uri":"https://www.mcc.gov/","name":"https://www.mcc.gov/","category":"website","ipAddress":null,"description":null,"engagementBriefTargetGroupTarget":{"id":"97ab896c-597a-4a9b-9b86-3ea73fdeb12f","sortOrder":0},"sortOrder":0,"tags":[{"id":"bc744424-2ab8-48c8-b938-c6d6abcdf500","name":"Website Testing","targetId":"1a8df6ef-80fd-4ec8-9569-a45f5f2f8f43"}],"recentChangeFlags":null},{"id":"1c6b0d92-5c9e-488e-b1b4-ac765316d84e","uri":"","name":"*.mcc.gov/","category":"website","ipAddress":null,"description":null,"engagementBriefTargetGroupTarget":{"id":"b94be20a-2c8b-47b4-9382-3bd8ab8aa9a9","sortOrder":0},"sortOrder":0,"tags":[{"id":"bc744424-2ab8-48c8-b938-c6d6abcdf500","name":"Website Testing","targetId":"1c6b0d92-5c9e-488e-b1b4-ac765316d84e"}],"recentChangeFlags":null}],"inScope":true,"sortOrder":0,"description":null,"rewardRange":null,"descriptionHtml":"\u003cp\u003eThe following systems/services are in scope:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eand all subdomains of mcc.gov\u003c/li\u003e\n\u003c/ul\u003e","rewardRangeData":{},"recentChangeFlags":null}],"resources":[],"engagement":{"id":"8a4b0d7b-d9bb-4008-b5d9-5a43a9886285","code":"mcc-vdp","state":"in_progress","endsAt":null,"bountyId":"60878cd7-1a86-4d2e-a56b-dec4b939c411","startsAt":"2021-07-29T13:00:00Z"},"engagementConfiguration":{"participation":"open","crowdSelectionStrategy":"none"}},"industryName":null,"methodologyName":null,"logoUrl":"https://logos.bugcrowdusercontent.com/logos/4ef9/7991/9219d5c0/5f32dc91dc0e02c8ceddd8e5e3934070_1519872156578.png","logoBackgroundColor":"#ffffff","displayDisclosureTerms":true,"coordinatedDisclosure":true,"collaborationEnabled":false,"participation":"open","rewardAllocation":"no_reward","engagementTypeDetail":{"iconVariant":"vdp","productLabel":"Vulnerability Disclosure","timeboxed":false},"pausedReason":null,"lastTransitionAt":"2021-07-29T13:00:00.000Z","cancellationReason":null,"statusLabel":"In progress","routesPaths":{"brief":"/engagements/mcc-vdp","changelogs":"/engagements/mcc-vdp/changelog","submissions":null,"announcements":"/engagements/mcc-vdp/announcements","hallOfFame":"/engagements/mcc-vdp/hall_of_fames","crowdstream":"/engagements/mcc-vdp/crowdstream"},"announcementsCount":0,"knownIssuesEnabled":true,"isDemo":false,"serviceLevel":"Priority Triage","submitReportUrl":"/engagements/mcc-vdp/submissions/new","methodologyUrl":null,"progressPercentage":0,"badgeVariant":null,"userBannedFromEngagement":null,"isLoggedIn":false,"loginUrl":"/user/sign_in","scopedSubmissionsUrl":"/submissions?engagement%5B%5D=mcc-vdp\u0026sort%5B%5D=submitted-desc","isFollowing":null,"credentialsUrl":null,"toggleSubscriptionUrl":"/mcc-vdp/engagement_subscribers","engagementChangelogsUrl":"/engagements/mcc-vdp/changelog","publishedAt":"2021-09-03T04:13:10.427Z","engagementChangelogUrl":"/engagements/mcc-vdp/changelog/acebb836-b601-4de6-85ce-755601ad0046","createUserFeedbacksUrl":"/engagements/mcc-vdp/feedbacks","engagementCrowdstreamUrl":"/engagements/mcc-vdp/crowdstream","acceptedSubmissionsEnabled":true,"disclosedReportsEnabled":true,"engagementsUrl":"/engagements","engagementPaymentDetailUrl":null,"shouldShowHideButton":false,"engagementHiddenData":{},"totalRewardPool":null,"vrtScopeRules":{"data":[]},"vrtVersion":"1.19.1","isSubmissionPublishThrottled":false,"showIdVerificationAlert":false,"identityVerificationSettingsUrl":"https://bugcrowd.com/h/settings/identity_verification","identityUrl":null}