{"id":"a101f7c7-7312-4a03-a012-61337b40da7d","engagementId":"68e19a3f-7b8a-4e43-8a89-6eb39a684926","data":{"brief":{"id":"acf9d8b0-4cc8-4dd8-aa87-c996cddb16b8","name":"Office of Surface Mining Reclamation and Enforcement: Vulnerability Disclosure Program","tagline":"Since August 3, 1977, the Office of Surface Mining Reclamation and Enforcement (OSMRE), along with its State and Tribal partners, community organizations and industry, has worked to ensure the cleanup of millions of acres of pre- Surface Mining Control and Reclamation Act (SMCRA) abandoned mine lands and the return of post-SMCRA mined lands to productive and beneficial use. ","description":"\u003ch2\u003eIntroduction:\u003c/h2\u003e\n\n\u003cp\u003eThe Department of the Interior (DOI), Office of Surface Mining Reclamation and Enforcement (OSMRE) 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\u003chr\u003e","industryTagId":"2a38890b-c88e-4bc0-8db0-02059f3fafe6","targetsOverview":"\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 DOI 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), \u003cstrong\u003eyou must stop your test, notify us immediately, and not disclose this data to anyone else.\u003c/strong\u003e\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\u003eNetwork denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.\u003c/li\u003e\n\u003cli\u003ePhysical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.\u003c/li\u003e\n\u003cli\u003eFull red-team penetration testing that involves unauthorized access to our servers.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eReporting a Vulnerability:\u003c/h2\u003e\n\n\u003cp\u003eInformation submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely DOI, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.\u003c/p\u003e\n\n\u003cp\u003eVulnerabilities may be reported to this Vulnerability Disclosure Program. \u003c/p\u003e\n\n\u003ch2\u003eWhat We Would Like to See From You:\u003c/h2\u003e\n\n\u003cp\u003eIn order to help us triage and prioritize submissions, we recommend that your reports:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDescribe the location the vulnerability was discovered and the potential impact of exploitation. \u003c/li\u003e\n\u003cli\u003eOffer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).\u003c/li\u003e\n\u003cli\u003eBe in English, if possible.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eWhat You Can Expect From Us:\u003c/h2\u003e\n\n\u003cp\u003eWhen you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eWithin 3 business days, we will acknowledge that your report has been received. \u003c/li\u003e\n\u003cli\u003eTo the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. \u003c/li\u003e\n\u003cli\u003eDOI does not provide payment to reporters for submitting vulnerabilities.\n\n\u003cul\u003e\n\u003cli\u003eReporters submitting vulnerabilities to DOI, in so doing, waive any claims to compensation. \u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eQuestions:\u003c/h2\u003e\n\n\u003cp\u003eQuestions regarding this policy may be sent to OSM-Cyber-Security@osmre.gov. If you aren’t sure whether a system is in scope or not, contact us at OSM-Cyber-Security@osmre.gov. We also invite you to contact us with suggestions for improving this policy.\u003c/p\u003e","safeHarborStatus":{"status":"partial","label":"Partial safe harbor","description":"This engagement provides a limited goodwill statement about not pursuing legal action related to security research."},"collaborationEnabled":true,"additionalInformation":"\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 OSMRE 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\u003cli\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 else.\u003c/li\u003e\n\u003c/ul\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\u003eNetwork denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.\u003c/li\u003e\n\u003cli\u003ePhysical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.\u003c/li\u003e\n\u003cli\u003eFull red-team penetration testing that involves unauthorized access to our servers.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eScope:\u003c/h2\u003e\n\n\u003cp\u003eThis policy applies to the following systems and services:\u003c/p\u003e\n\n\u003cp\u003e\u003cem\u003e*.osmre.gov.\u003c/em\u003e\u003c/p\u003e\n\n\u003cp\u003eAny service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their Disclosure Policy (if any). If you aren’t sure whether a system is in scope or not, contact us at osm-csirt@osmre.gov before starting your research (or at the security contact for the system’s domain name listed in the \u003ca href=\"https://domains.dotgov.gov/dotgov-web/registration/whois.xhtml\" rel=\"nofollow noreferrer\" target=\"_blank\"\u003e.gov WHOIS\u003c/a\u003e). \u003c/p\u003e\n\n\u003cp\u003eThough OSMRE develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time. \u003c/p\u003e\n\n\u003ch2\u003eReporting a Vulnerability:\u003c/h2\u003e\n\n\u003cp\u003eInformation submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely OSMRE, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.\u003c/p\u003e\n\n\u003cp\u003eVulnerabilities may be reported to this Vulnerability Disclosure Program. \u003c/p\u003e\n\n\u003ch2\u003eWhat We Would Like to See From You:\u003c/h2\u003e\n\n\u003cp\u003eIn order to help us triage and prioritize submissions, we recommend that your reports:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDescribe the location the vulnerability was discovered and the potential impact of exploitation. \u003c/li\u003e\n\u003cli\u003eOffer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).\u003c/li\u003e\n\u003cli\u003eBe in English, if possible.\u003c/li\u003e\n\u003cli\u003eWhat You Can Expect From Us\u003c/li\u003e\n\u003cli\u003eWhen you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2\u003eWhat You Can Expect From Us:\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003eWithin 3 business days, we will acknowledge that your report has been received. \u003c/li\u003e\n\u003cli\u003eTo the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. \u003c/li\u003e\n\u003cli\u003eOSMRE does not provide payment to reporters for submitting vulnerabilities.\n\n\u003cul\u003e\n\u003cli\u003eReporters submitting vulnerabilities to OSMRE, in so doing, waive any claims to compensation. \u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e"},"scope":[{"id":"39a851db-46bf-4878-8acd-78758271fdb1","name":"In Scope Targets","targets":[{"id":"c3c632d3-1198-470e-a381-0ed8d902dd02","uri":"","name":"*.osmre.gov.","category":"website","ipAddress":"","description":null,"engagementBriefTargetGroupTarget":{"id":"8ece7767-e2a5-4974-8aa2-b08463d1cda2","sortOrder":0},"sortOrder":0,"tags":[{"id":"45e28558-ada7-4f38-b087-fb0e6ac31e0d","name":"AWS","targetId":"c3c632d3-1198-470e-a381-0ed8d902dd02"},{"id":"3a3487a7-9abf-45f0-8057-51dabed20371","name":"Drupal","targetId":"c3c632d3-1198-470e-a381-0ed8d902dd02"},{"id":"a51a78cb-e0a6-4043-a736-335dec2d238c","name":"jQuery","targetId":"c3c632d3-1198-470e-a381-0ed8d902dd02"},{"id":"bc744424-2ab8-48c8-b938-c6d6abcdf500","name":"Website Testing","targetId":"c3c632d3-1198-470e-a381-0ed8d902dd02"},{"id":"abbd0575-727e-4565-8046-f7fa78eaf368","name":"PHP","targetId":"c3c632d3-1198-470e-a381-0ed8d902dd02"}],"recentChangeFlags":null}],"inScope":true,"sortOrder":0,"description":null,"rewardRange":null,"descriptionHtml":"\u003cp\u003eThis policy applies to the following systems and services:\u003c/p\u003e","rewardRangeData":{},"recentChangeFlags":null},{"id":"3d8af107-35ba-44dc-92b5-568ee939dfa9","name":"Out of Scope Targets","targets":[{"id":"41c0c544-1127-4ad8-8c0b-6af10df017b2","uri":"","name":"Anything not explicitly listed as 'In Scope'","category":"website","ipAddress":"","description":null,"engagementBriefTargetGroupTarget":{"id":"5fb3b0db-401b-4666-91ea-8e13011bf141","sortOrder":0},"sortOrder":0,"tags":null,"recentChangeFlags":null}],"inScope":false,"sortOrder":1,"description":null,"rewardRange":null,"descriptionHtml":"\u003cp\u003eAny service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their Disclosure Policy (if any). If you aren’t sure whether a system is in scope or not, contact us at OSM-Cyber-Security@osmre.gov before starting your research (or at the security contact for the system’s domain name listed in the \u003ca href=\"https://domains.dotgov.gov/dotgov-web/registration/whois.xhtml\" rel=\"nofollow noreferrer\" target=\"_blank\"\u003e.gov WHOIS\u003c/a\u003e). \u003c/p\u003e\n\n\u003cp\u003eThough we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time. \u003c/p\u003e","rewardRangeData":{},"recentChangeFlags":null}],"resources":[],"engagement":{"id":"68e19a3f-7b8a-4e43-8a89-6eb39a684926","code":"osmre-vdp","state":"in_progress","endsAt":null,"bountyId":"8e5836a6-8c2a-4fb9-a56d-ce5bc6c7641e","startsAt":"2025-01-07T16:55:16Z"},"engagementConfiguration":{"participation":"open","crowdSelectionStrategy":"none"}},"industryName":"Government","methodologyName":null,"logoUrl":"https://logos.bugcrowdusercontent.com/logos/1a6b/92a5/6224372a/72e83ece89d57bd99dc67f329c7937b2_OSMLogoColor.png","logoBackgroundColor":"#ffffff","displayDisclosureTerms":true,"coordinatedDisclosure":true,"collaborationEnabled":true,"participation":"open","rewardAllocation":"no_reward","engagementTypeDetail":{"iconVariant":"vdp","productLabel":"Vulnerability Disclosure","timeboxed":false},"pausedReason":null,"lastTransitionAt":"2025-01-07T16:55:16.891Z","cancellationReason":null,"statusLabel":"In progress","routesPaths":{"brief":"/engagements/osmre-vdp","changelogs":"/engagements/osmre-vdp/changelog","submissions":null,"announcements":"/engagements/osmre-vdp/announcements","hallOfFame":"/engagements/osmre-vdp/hall_of_fames","crowdstream":"/engagements/osmre-vdp/crowdstream"},"announcementsCount":0,"knownIssuesEnabled":true,"isDemo":false,"serviceLevel":"Priority Triage","submitReportUrl":"/engagements/osmre-vdp/submissions/new","methodologyUrl":null,"progressPercentage":0,"badgeVariant":null,"userBannedFromEngagement":null,"isLoggedIn":false,"loginUrl":"/user/sign_in","scopedSubmissionsUrl":"/submissions?engagement%5B%5D=osmre-vdp\u0026sort%5B%5D=submitted-desc","isFollowing":null,"credentialsUrl":null,"toggleSubscriptionUrl":"/osmre-vdp/engagement_subscribers","engagementChangelogsUrl":"/engagements/osmre-vdp/changelog","publishedAt":"2025-01-21T18:18:46.081Z","engagementChangelogUrl":"/engagements/osmre-vdp/changelog/a101f7c7-7312-4a03-a012-61337b40da7d","createUserFeedbacksUrl":"/engagements/osmre-vdp/feedbacks","engagementCrowdstreamUrl":"/engagements/osmre-vdp/crowdstream","acceptedSubmissionsEnabled":false,"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}