Viewing Collection: web_static_analysis_generate_content_discovery_report

6a0d95f37c0a72167716743e

Wed May 20 2026 11:07:31 GMT+0000 (Coordinated Universal Time)

https://pro.anveshaktool.in/

generate_content_discovery_report

{
  "url": "https://pro.anveshaktool.in/",
  "category": "content_discovery",
  "timestamp": "2026-05-20T11:07:31.066504+00:00",
  "report": "### [ERROR] LLM generation failed after 5 retries.\nLast Error: Read timeout on endpoint URL: \"https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse\"",
  "summary": {
    "total": 63
  }
}

{
  "total": 63
}

6a0db69929c37a9fa9617cfa

Wed May 20 2026 13:26:49 GMT+0000 (Coordinated Universal Time)

https://pro.anveshaktool.in/

generate_content_discovery_report

{
  "url": "https://pro.anveshaktool.in/",
  "category": "content_discovery",
  "timestamp": "2026-05-20T13:26:49.266729+00:00",
  "report": "### [ERROR] LLM generation failed after 5 retries.\nLast Error: Read timeout on endpoint URL: \"https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse\"",
  "summary": {
    "total": 63
  }
}

{
  "total": 63
}

6a0e320a8e04da6db55e8e34

Wed May 20 2026 22:13:30 GMT+0000 (Coordinated Universal Time)

https://springs.com.pk

generate_content_discovery_report

{
  "url": "https://springs.com.pk",
  "category": "content_discovery",
  "timestamp": "2026-05-20T22:13:30.188395+00:00",
  "report": "",
  "summary": {
    "total": 0
  }
}

{
  "total": 0
}

6a0e74c95a5286f67db8038a

Thu May 21 2026 02:58:17 GMT+0000 (Coordinated Universal Time)

https://www.veltris.com/

generate_content_discovery_report

{
  "url": "https://www.veltris.com/",
  "category": "content_discovery",
  "timestamp": "2026-05-21T02:58:17.753930+00:00",
  "report": "### [ERROR] LLM generation failed after 5 retries.\nLast Error: ### Critical: LLM Generation Failures Due to Timeout and Context Length Limits\n\n#### Finding 1: Repeated LLM Generation Timeouts\n- **Severity**: Critical\n- **Description**: Multiple attempts to generate content using the Qwen model via AWS Bedrock resulted in read timeouts. This indicates that the service was either unresponsive or took longer than allowed to return a response.\n- **Affected Endpoint**: `https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse`\n- **Occurrences**: Observed across 9 out of 10 analysis chunks.\n- **Technical Detail**:\n  ```\n  [ERROR] LLM generation failed after 5 retries.\n  Last Error: Read timeout on endpoint URL: \"https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse\"\n  ```\n- **Business Impact**: Service unavailability can lead to denial of service for dependent applications, affecting user experience and operational continuity.\n- **Remediation Steps**:\n  1. Investigate network latency between client and AWS Bedrock region (`ap-south-1`).\n  2. Optimize request payload size to reduce processing time.\n  3. Implement exponential backoff with jitter in retry logic.\n  4. Consider switching to a geographically closer AWS region if applicable.\n  5. Monitor AWS Bedrock service health dashboard for ongoing issues.\n\n#### Finding 2: Input Token Limit Exceeded\n- **Severity**: Critical\n- **Description**: A specific error occurred due to exceeding the maximum context window supported by the Qwen model. The combined input and output token count surpassed the limit of 131,072 tokens.\n- **Error Message**:\n  ```\n  ErrorEvent { error: APIError { type: \"BadRequestError\", code: Some(400), message: \"This model's maximum context length is 131072 tokens. However, you requested 16000 output tokens and your prompt contains at least 115073 input tokens, for a total of at least 131073 tokens. Please reduce the length of the input prompt or the number of requested output tokens.\" }}\n  ```\n- **Root Cause**: Prompt engineering did not account for model limitations; large prompts were submitted without truncation or summarization strategies.\n- **Business Impact**: Inability to process large inputs may prevent core functionality from executing correctly, especially in use cases involving document analysis or long-form reasoning tasks.\n- **Remediation Steps**:\n  1. Preprocess input data to truncate or summarize content before submission.\n  2. Dynamically adjust output token limits based on remaining available context space.\n  3. Introduce chunking mechanisms to split oversized requests into smaller segments.\n  4. Log oversized requests for further review and optimization.\n  5. Update application logic to validate prompt sizes against known model constraints prior to sending.",
  "summary": {
    "total": 3834
  }
}

{
  "total": 3834
}

6a0eb5923bde3f52b4af3cc4

Thu May 21 2026 07:34:42 GMT+0000 (Coordinated Universal Time)

https://www.veltris.com/

generate_content_discovery_report

{
  "url": "https://www.veltris.com/",
  "category": "content_discovery",
  "timestamp": "2026-05-21T07:34:42.901364+00:00",
  "report": "### [ERROR] LLM generation failed after 5 retries.\nLast Error: ### Findings Summary – Content Discovery\n\nNo actionable findings were identified during the content discovery phase. All attempts to analyze the target using the specified LLM-based tooling resulted in repeated failures due to infrastructure-level timeouts and validation errors.\n\n---\n\n### Critical Issues\n\n#### LLM Generation Timeout Errors  \n**Severity:** Critical  \n**Description:** Repeated timeout errors occurred when attempting to invoke the Amazon Bedrock endpoint for model inference. This prevented any meaningful analysis from being performed.  \n**Endpoint:** `https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse`  \n**Error Message:**  \n```\nRead timeout on endpoint URL\n```  \n**Occurrences:** 9 out of 10 chunks reported this exact failure after 5 retries.  \n\n**Technical Details:**  \n- The consistent read timeout indicates either an unresponsive backend service or network misconfiguration affecting communication with the model API.\n- These timeouts occurred before any application-layer logic could be evaluated, rendering the testing process ineffective.\n\n**Business Impact:**  \n- Complete inability to perform automated content discovery tasks.\n- Potential degradation in overall assessment quality if alternative methods are not employed.\n\n**Remediation Steps:**  \n1. Verify that the Bedrock runtime environment is operational and responsive.\n2. Check AWS region availability and ensure there are no ongoing service disruptions.\n3. Validate IAM permissions and authentication tokens used to access the model.\n4. Consider increasing timeout thresholds or switching to a more stable model variant for future assessments.\n\n---\n\n### High Issues\n\n#### Context Length Validation Failure  \n**Severity:** High  \n**Description:** One request exceeded the maximum allowed token limit for the selected model (`qwen.qwen3-coder-480b-a35b-v1:0`).  \n**Error Type:** `ValidationException`  \n**Error Message:**  \n```\n{\"error\":{\"code\":\"validation_error\",\"message\":\"ErrorEvent { error: APIError { type: \\\"BadRequestError\\\", code: Some(400), message: \\\"This model's maximum context length is 131072 tokens. However, you requested 16000 output tokens and your prompt contains at least 115073 input tokens, for a total of at least 131073 tokens. Please reduce the length of the input prompt or the number of requested output tokens. (parameter=input_tokens, value=115073)\\\"}}}}\n```  \n\n**Technical Details:**  \n- Total tokens consumed = Input tokens (≥115,073) + Output tokens (16,000) = ≥131,073 tokens  \n- Model’s max supported tokens = 131,072  \n- Exceeded by at least 1 token  \n\n**Business Impact:**  \n- Inability to process large inputs or generate long outputs within the current configuration.\n- Risk of data truncation or incomplete processing if mitigation is not applied.\n\n**Remediation Steps:**  \n1. Reduce the size of the input prompt to stay under the model’s maximum context window.\n2. Lower the requested number of output tokens accordingly.\n3. Implement pre-processing logic to chunk large payloads prior to submission.\n4. Evaluate whether a larger-context model is available and suitable for use.\n\n--- \n\n### Medium / Low / Informational Findings\n\nNone identified beyond those already detailed above. Due to systemic failures in execution, further enumeration did not yield additional vulnerabilities or observations.",
  "summary": {
    "total": 3834
  }
}

{
  "total": 3834
}

6a0fb6ef1194eafc27fd3eef

Fri May 22 2026 01:52:47 GMT+0000 (Coordinated Universal Time)

https://ep.gov.pk/

generate_content_discovery_report

{
  "url": "https://ep.gov.pk/",
  "category": "content_discovery",
  "timestamp": "2026-05-22T01:52:47.837913+00:00",
  "report": "## Findings Summary\n\nAll findings have been consolidated and organized by severity. Since all findings fall under the **Info** severity category, they are presented collectively below in alphabetical order by URL path for clarity and completeness.\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/ |\n\n**Description**  \nDiscovery of the directory `/ep_Complaint/` indicates a dedicated section for handling complaints. Directory listings or default pages under this path may reveal additional endpoints or administrative interfaces. Even if protected, the mere existence expands the attack surface.\n\n**Attack Scenario (Proof of Concept)**  \nUsing automated tools like Dirbuster or Gobuster, an attacker can probe subdirectories and files beneath `/ep_Complaint/` to find login portals, upload forms, or configuration files.\n\nCommand:\n```bash\ngobuster dir -u https://ep.gov.pk/ep_Complaint/ -w common.txt\n```\n\n**Business Impact**  \nPotential entry point for unauthorized complaint submissions, phishing campaigns, or brute-force attacks targeting weak authentication systems.\n\n**Remediation**  \nDisable directory browsing and enforce strong access controls on complaint management modules. Monitor access logs for suspicious activity around this area.\n\nReference: CWE-548 – Exposure of Information Through Directory Listing\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/default.aspx\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/default.aspx |\n\n**Description**  \nThe discovery of `/ep_Complaint/default.aspx` reveals a complaint submission portal hosted under the domain. Although currently returning a valid response (HTTP 200), further investigation should determine whether this interface allows anonymous submissions, lacks rate limiting, or exposes personally identifiable information (PII).\n\nAutomated scanners frequently identify such endpoints when performing recursive scans or spidering web applications.\n\n**Attack Scenario (Proof of Concept)**  \n1. Using Burp Suite Spider or ZAP, an attacker discovers the endpoint.\n2. Submitting test complaints manually or via script:\n   ```http\n   POST /ep_Complaint/default.aspx HTTP/1.1\n   Host: ep.gov.pk\n   Content-Type: application/x-www-form-urlencoded\n\n   name=test&email=test@example.com&complaint=Test+message\n   ```\n3. If no CAPTCHA or throttling exists, mass spamming becomes feasible.\n\nAdditionally, if error messages leak database schema details or stack traces, exploitation opportunities increase.\n\n**Business Impact**  \nUnrestricted complaint portals can become spam targets, leading to resource exhaustion, reputational harm, and possible abuse for phishing or social engineering campaigns. In worst-case scenarios, PII leakage occurs due to poor validation practices.\n\n**Remediation**  \n- Enforce strong anti-bot measures such as reCAPTCHA v3.\n- Apply rate-limiting per IP address or session.\n- Validate and sanitize all form fields strictly.\n- Mask or anonymize submitted data until reviewed internally.\n- Monitor logs for suspicious activity related to complaint submissions.\n\nReference: [CWE-20: Improper Input Validation](https://cwe.mitre.org/data/definitions/20.html)\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/images\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/images |\n\n**Description**  \nAccess to the `/ep_Complaint/images` directory returns an HTTP 403 Forbidden response, suggesting that direct listing or browsing is blocked. However, the mere existence of this path implies there are likely image assets stored beneath it, potentially referenced elsewhere in the application.\n\nDirectory enumeration tools will flag such responses because even though access is denied, the path itself still contributes to the overall attack surface profile.\n\n**Attack Scenario (Proof of Concept)**  \n1. Automated scanner identifies the forbidden directory:\n   ```bash\n   dirsearch -u https://ep.gov.pk/ep_Complaint/\n   ```\n2. Reports back:\n   ```\n   [403] /ep_Complaint/images\n   ```\n3. Attacker tries common filenames inside the folder:\n   ```\n   GET /ep_Complaint/images/logo.png\n   GET /ep_Complaint/images/banner.jpg\n   ```\n\nEven if individual files aren't exposed, knowing their structure helps tailor future attacks against upload/download mechanisms.\n\n**Business Impact**  \nWhile seemingly benign, revealing internal directory structures aids attackers in crafting more precise payloads. Additionally, misconfigured permissions might allow bypasses laterally across the filesystem.\n\n**Remediation**  \n- Remove unused or redundant directories entirely.\n- Ensure proper `.htaccess` rules or IIS settings prevent directory listing.\n- Rename generic folders to obscure names (e.g., `/assets/img/complaints_v2/`).\n- Periodically review and prune obsolete assets.\n\nReference: [OWASP Testing Guide – Directory Browsing](https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/02-Configuration_and_Deployment_Management_Testing/02-Test_Application_Platform_Configuration)\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/images/\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/images/ |\n\n**Description**  \nSimilar to the previous entry but with a trailing slash, this path also yields a 403 Forbidden response. This distinction matters in certain web servers where `/images` vs `/images/` behaves differently—sometimes triggering default document lookups or index generation attempts.\n\nDespite both yielding identical results, distinguishing between them helps refine scanning accuracy and avoid false positives/negatives.\n\n**Attack Scenario (Proof of Concept)**  \n1. Scanner probes both variations:\n   ```bash\n   curl -I https://ep.gov.pk/ep_Complaint/images\n   curl -I https://ep.gov.pk/ep_Complaint/images/\n   ```\n2. Both respond with:\n   ```\n   HTTP/1.1 403 Forbidden\n   Server: Microsoft-IIS/10.0\n   ```\n3. Attacker infers that the directory exists but is protected, prompting deeper inspection of parent or sibling paths.\n\n**Business Impact**  \nSame implications as above—increased visibility into application architecture without immediate compromise. Still, each additional known path expands the footprint for lateral movement or privilege escalation vectors.\n\n**Remediation**  \n- Normalize handling of trailing slashes in routing configurations.\n- Redirect one version to another consistently to reduce ambiguity.\n- Apply consistent access policies regardless of URI format.\n- Review server logs periodically for repeated 403 errors indicative of probing.\n\nReference: [RFC 3986 – Uniform Resource Identifier (URI): Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-6.2.3)\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/ScriptResource.axd?...\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/ScriptResource.axd?d=z8yOly3moIAZ5s6gAn3zcPPhcH7FjuJHN3dKJEw606dU2sfe6WAYyLNdt5YsnXwkrYiffbGtmrgjXzVpbLE0a0gFS-CS4FiAY6uH8qRaFcDC46mjMZ7JSw-fQCV-Cd8xtYVYtU4v4RGNRXkWAyZSwxqRQegEcgHLkkmoLhjxMyU1&t=ffffffff9b7d03cf |\n\n**Description**  \nThe discovery of a ScriptResource.axd handler reveals dynamically generated JavaScript files typically used in ASP.NET applications. These resources often contain client-side logic, localization strings, or UI components. Their exposure does not directly indicate vulnerability but contributes to fingerprinting capabilities for attackers.\n\n**Attack Scenario (Proof of Concept)**  \nAttackers can analyze these script resources to understand application behavior, identify frameworks/libraries in use, and potentially locate vulnerabilities within them. For instance, outdated versions of jQuery or other libraries embedded here could introduce XSS risks.\n\nRequest Example:\n```http\nGET /ep_Complaint/ScriptResource.axd?d=[truncated]&t=ffffffff9b7d03cf HTTP/1.1\nHost: ep.gov.pk\n```\n\n**Business Impact**  \nExposure of internal scripts aids reconnaissance efforts and may assist in crafting more targeted attacks against known weaknesses in third-party dependencies.\n\n**Remediation**  \nEnsure that only essential scripts are exposed and that they are minified and obfuscated where possible. Regularly update framework versions and remove unused handlers from production environments.\n\nReference: CWE-200 – Information Exposure\n\n---\n\n### Content Discovery: ep.gov.pk /ep_Complaint/WebResource.axd?...\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/ep_Complaint/WebResource.axd?d=BbSBvXhD8EthEiTR5PhSkrKBGc8JeJ6dfeEu5UukXLtukekPyk-MC0s9l10uBFNKzlf7za_l1Q20VlmHYl5w8s4UGDuQJMrJWeea5dLDXd01&t=637568388846384355 |\n\n**Description**  \nWebResource.axd serves static content such as images, CSS, or compiled scripts in ASP.NET applications. Its presence confirms the use of .NET Web Forms technology stack. Like ScriptResource.axd, its exposure offers little direct threat but enhances attacker situational awareness.\n\n**Attack Scenario (Proof of Concept)**  \nAttackers can inspect returned content to determine file paths, component versions, and styling choices. This helps build a profile of the site's structure and potentially uncover deprecated or vulnerable assets.\n\nExample:\n```http\nGET /ep_Complaint/WebResource.axd?d=[encoded_string]&t=timestamp HTTP/1.1\nHost: ep.gov.pk\n```\n\n**Business Impact**  \nReveals implementation details that could aid lateral movement during deeper compromise attempts.\n\n**Remediation**  \nAvoid exposing unnecessary debugging symbols or development artifacts. Consider bundling and compressing resources to obscure internal naming conventions.\n\nReference: CWE-200 – Information Exposure\n\n---\n\n### Content Discovery: ep.gov.pk /logout.asp\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/logout.asp |\n\n**Description**  \nThe logout page (`/logout.asp`) represents a session termination mechanism. Although standard practice, improper handling of sessions upon logout—such as failure to invalidate tokens or redirect securely—can leave users vulnerable post-logout.\n\n**Attack Scenario (Proof of Concept)**  \nIf the logout process doesn’t properly destroy session cookies or tokens, an attacker who gains physical access after a user logs out may still retain valid credentials. Additionally, lack of secure redirection could result in open redirects or session fixation opportunities.\n\nSample Request:\n```http\nGET /logout.asp HTTP/1.1\nHost: ep.gov.pk\nCookie: ASPSESSIONID=abc123xyz;\n```\n\n**Business Impact**  \nRisk of account hijacking, especially in shared computing environments or kiosks. Could undermine trust in identity management processes.\n\n**Remediation**  \nEnsure complete destruction of session identifiers upon logout. Redirect users to a neutral landing page and clear browser storage (cookies/localStorage). Enforce HTTPS to prevent token interception.\n\nReference: CWE-613 – Insufficient Session Expiration\n\n---\n\n### Content Discovery: ep.gov.pk /sitemap.asp\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | https://ep.gov.pk/sitemap.asp |\n\n**Description**  \nA sitemap file (`/sitemap.asp`) has been identified, returning a successful HTTP status code (200 OK). This file typically lists key pages within a website to assist search engines in indexing content. However, from a security perspective, it serves as an easy map for attackers to locate hidden or less-obvious paths.\n\nSuch files are commonly indexed automatically during reconnaissance phases using tools like `nuclei`, `whatweb`, or simple directory brute-forcing techniques.\n\n**Attack Scenario (Proof of Concept)**  \n1. Attacker runs a basic scan:\n   ```bash\n   curl -I https://ep.gov.pk/sitemap.asp\n   ```\n2. Response confirms existence:\n   ```\n   HTTP/1.1 200 OK\n   Content-Type: text/html\n   ```\n3. Download and parse the sitemap:\n   ```xml\n   <url>\n     <loc>https://ep.gov.pk/admin/login</loc>\n     <lastmod>2024-01-01</lastmod>\n   </url>\n   ```\n4. With knowledge of administrative interfaces, targeted attacks begin.\n\n**Business Impact**  \nExposing a sitemap provides adversaries with a roadmap of available resources, including potentially sensitive areas like admin panels, API gateways, or staging environments. This significantly reduces time-to-exploit and increases risk exposure.\n\n**Remediation**  \n- Restrict public access to sitemaps via robots.txt or IP whitelisting.\n- Exclude sensitive paths from being listed in sitemaps.\n- Regularly audit and update sitemap contents to ensure only intended pages are exposed.\n- Consider serving different versions of sitemaps depending on user roles or context.\n\nReference: [OWASP Top Ten – A07:2021 Identification and Authentication Failures](https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/)\n\n---\n\n### Content Discovery: ep.gov.pk /tariff/emsp_tariff.aspx?Country_Name=...\n\n| Field | Value |\n|---|---|\n| Severity | Info |\n| CVSS Score | 0.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N) |\n| Category | content_discovery |\n| Asset / URL | Multiple tariff endpoints with varying parameters |\n\n**Description**  \nMultiple instances of the `/tariff/emsp_tariff.aspx` endpoint were discovered, accepting query parameters such as `Country_Name`, `Type`, and `Zone`. These endpoints dynamically render tariff-related information based on user input. While not inherently insecure, exposing such functionality without proper access controls or rate limiting can lead to enumeration attacks, scraping of sensitive data, or abuse via automated tools.\n\nThe server responds with a 200 OK status code, indicating successful retrieval of content. This may allow attackers to map out available resources and understand internal logic used by the application.\n\n**Attack Scenario (Proof of Concept)**  \nAn attacker could use tools like Burp Suite Intruder or custom scripts to enumerate all possible combinations of countries, types, and zones to extract tariff-related data across multiple regions. Example request:\n\n```http\nGET /tariff/emsp_tariff.aspx?Country_Name=DENMARK&Type=Document&Zone=Zone%201 HTTP/1.1\nHost: ep.gov.pk\n```\n\nAutomated discovery using `ffuf` might look like this:\n```bash\nffuf -u \"https://ep.gov.pk/tariff/emsp_tariff.aspx?Country_Name=FUZZ&Type=Document&Zone=Zone%201\" -w countries.txt\n```\n\n**Business Impact**  \nExposure of tariff structures and related metadata may provide competitors with strategic insights into pricing models or trade policies. Additionally, excessive crawling or brute-force enumeration could strain server resources, leading to performance degradation or denial-of-service conditions.\n\n**Remediation**  \n- Implement rate-limiting mechanisms at the web server or application level.\n- Restrict access to authenticated users where appropriate.\n- Add CAPTCHA challenges or IP-based throttling for repeated requests.\n- Log and monitor unusual traffic patterns indicative of scraping or enumeration attempts.\n\nReference: [OWASP-2017 A6 - Security Misconfiguration](https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration)",
  "summary": {
    "total": 486
  }
}

{
  "total": 486
}

6a10022959489bda47358755

Fri May 22 2026 07:13:45 GMT+0000 (Coordinated Universal Time)

https://ep.gov.pk/

generate_content_discovery_report

{
  "url": "https://ep.gov.pk/",
  "category": "content_discovery",
  "timestamp": "2026-05-22T07:13:45.964938+00:00",
  "report": "### Content Discovery Findings\n\nNo content discovery findings were identified during the assessment. Both analysis chunks returned identical LLM generation errors indicating timeouts on the endpoint URL: \"https://bedrock-runtime.ap-south-1.amazonaws.com/model/qwen.qwen3-coder-480b-a35b-v1%3A0/converse\". This technical failure prevented the identification and analysis of potential content discovery vulnerabilities that would typically include issues such as exposed administrative interfaces, backup files, configuration files, or other sensitive directories and files that may be accessible through systematic enumeration techniques.",
  "summary": {
    "total": 482
  }
}

{
  "total": 482
}

6a1430837175cb3fbedb1c64

Mon May 25 2026 11:20:35 GMT+0000 (Coordinated Universal Time)

https://ep.gov.pk/

generate_content_discovery_report

{
  "total": 482
}

6a15636954b4b0d970835f09

Tue May 26 2026 09:10:01 GMT+0000 (Coordinated Universal Time)

https://ep.gov.pk/

generate_content_discovery_report

{
  "total": 482
}

6a1f31f5cde3bf870411ebfc

Tue Jun 02 2026 19:41:41 GMT+0000 (Coordinated Universal Time)

https://onmark.co.in/nmu/

generate_content_discovery_report

{
  "total": 1312
}