Sari la conținut

Coșul tău

Coșul tău este gol.

Adaugă un serviciu din magazin și te așteaptă aici până finalizezi comanda.

Vezi magazinul

După plată

  1. Echipa citește detaliile tale și îți scrie pe email, de obicei într-o zi lucrătoare.
  2. Urmărești progresul și vorbești cu echipa în portalul clienților.
Subtotal

Servicii cu plată unică, prețuri în USD.

Finalizează comanda Vezi coșul

Anonimizat dintr-o evaluare reală EWC

Exemplu de raport

Rapoarte reale de pentest. Anonimizate.

Două evaluări black-box livrate de noi: un site în stare critică, unul care a rezistat în mare parte. Datele clienților au fost eliminate. Constatările au rămas.

Conținutul raportului este în engleză, așa cum a fost livrat.

EWC / CybersecurityAnonimizat dintr-o evaluare reală EWC

Test de penetrare și evaluare de securitate

Pregătit pentru
Evaluare
Externă, neautentificată
Raport
Raportul A, 41 de pagini
Referință
  • 3Ridicat
  • 7Mediu
  • 7Scăzut
  • 5Info

ConfidențialPagina 1 din 41

01Rezultatele evaluăriiRaportul A

Securitatea dintr-o privire

Risc general

Critic

Evaluat critic: o expunere la nivel de server nu a putut fi exclusă din exterior, iar mai multe constatări se combină.

Constatări după gravitate

22 constatări

  • Critic0
  • Ridicat3
  • Mediu7
  • Scăzut7
  • Info5
  • 10constatări ridicate și medii de rezolvat întâi
  • 41pagini în raportul livrat
  • 12clase de atac care au rezistat

02Rezumat executiv

Ce citește proprietarul întâi

A server-level exposure that could not be ruled out from outside, open backend access and weak email protection. Patch first, then close the doors.

Implicații pentru afacere

The main risks: compromise of the publishing server, takeover of editor accounts and bulk harvesting of the site's directory. Missing email authentication makes the brand easy to impersonate.

Priorități imediate

Confirm and patch the server runtime. Update the CMS, protect the login and fix upload validation. Review what the public API returns and switch on email authentication.

Controale care au rezistat

No SQL injection, cross-site scripting, file inclusion, open redirect or permissive cross-origin access was confirmed in the paths examined.

03Scop și metodologie

Ce s-a testat și cum

Țintă
A publishing website on a popular CMS, with a separate API host
Test
External black-box penetration test
Acces
Unauthenticated, no source code
Fereastră
A single overnight testing window

Metodă

  1. 01DNS and certificate reconnaissance
  2. 02Content and route discovery
  3. 03Parameter and injection testing
  4. 04Header and cookie review
  5. 05TLS protocol checks
  6. 06API enumeration
  7. 07Upload validation
  8. 08Targeted exploit attempts

În scop

  • Public website
  • API and CMS host
  • TLS endpoints
  • DNS and email domain records

Reguli de angajare

  • No content, account or setting was edited or deleted
  • Only additive test submissions, to exercise the upload pipeline
  • Request rates kept low to avoid disruption
  • Retrieved data handed back to the client

În afara scopului

  • Third-party service infrastructure
  • Signed-in CMS testing
  • Social engineering
  • Physical testing
  • Denial-of-service load

Limite declarate

  • The exact runtime patch level cannot be proven from outside
  • The site's web firewall stopped one exploit probe at its first stage
  • Whether an uploaded file could run was not verifiable

Suprafața de atac

  1. 01

    Web firewall and edge

    Public HTTP and TLS entry point for both hosts.

  2. 02

    Public website

    Dynamic pages, search, filters and a public submission form with uploads.

  3. 03

    API and CMS host

    Content API, the editors' login and integration endpoints.

  4. 04

    Email domain

    Sender policy, signing keys and DNS assurance records.

04Registrul constatărilor

22 de constatări, ordonate

  1. F-01RidicatServer runtime needs urgent patch verificationServer
  2. F-02RidicatAnonymous API access exposes the content archive and contact dataAPIAnaliză completă
    7.5CVSS 3.1estimatConfirmed

    Pe înțelesul tuturor

    The publishing API lets anyone download the content archive and directory records without signing in, contact details included.

    Implicații pentru afacere

    An attacker can collect the directory in bulk and use named contacts and organisation details to write convincing phishing emails or phone scams. The archive itself can be copied at scale.

    Ce arată dovezile

    Anonymous requests returned thousands of records across several collections, including email addresses, phone numbers and postal addresses. Three requests were enough to list the collections and page through them.

    Cereri capturate, generalizate
    GET /api/types                 200  every content type listedGET /api/directory?limit=1     200  total: GET /api/directory?limit=100   200  full records, contact fields
    1. Acțiune recomandată

      Agree which records and fields are meant to be public. Withhold private fields and unneeded metadata without breaking the public site, and add proportionate request limits.

    2. Cum se verifică remedierea

      Compare anonymous API responses with the agreed publication rules. Private fields are withheld; public pages still work.

  3. F-03RidicatCMS core is behind the current security releaseCMS
  4. F-04MediuA trailing slash bypasses the login-page blockSign-inAnaliză completă
    5.3CVSS 3.1estimatObserved

    Pe înțelesul tuturor

    A rule blocks the normal login address. Add a slash to the end and the sign-in form loads anyway.

    Implicații pentru afacere

    The block meant to hide the login form can be walked around. Together with the missing throttling in F-05, editor accounts are open to password guessing and credential stuffing.

    Ce arată dovezile

    The login address returned 403 Forbidden. The same address with a trailing slash returned 200 and the full sign-in form. The admin routes stayed blocked.

    Cereri capturate, generalizate
    GET /login     403  ForbiddenGET /login/    200  full sign-in formGET /admin/    403  Forbidden
    1. Acțiune recomandată

      Apply the restriction to every equivalent path. Normalise paths and test trailing-slash, encoded and double-slash variants. Keep MFA and login throttling.

    2. Cum se verifică remedierea

      Every equivalent login address gets the same decision, and real editors can still sign in.

  5. F-05MediuLogin form has no observed throttlingSign-in
  6. F-06MediuUpload form accepts falsely labelled image filesUploadsAnaliză completă
    5.4CVSS 3.1estimatValidation failure

    Pe înțelesul tuturor

    The upload form accepted a file that was not an image, because the upload said it was a JPEG. The label a browser sends cannot be trusted.

    Implicații pentru afacere

    Trusting the sender's label lets non-image content into the upload pipeline. If such a file were stored and run as code, it could lead to server-side code execution.

    Ce arată dovezile

    A harmless script file labelled image/jpeg was accepted and redirected to the success page. The same bytes labelled honestly were rejected. Size and count limits held. Where the file was stored could not be recovered.

    Cereri capturate, generalizate
    POST /submit  note.txt  type=text/plain   rejectedPOST /submit  probe     type=image/jpeg   302  successPOST /submit  oversized photo             rejected, size limit
    1. Acțiune recomandată

      Check content with a maintained image decoder, allow only the formats you need, re-encode images and generate safe names. Store uploads outside executable paths with script execution off.

    2. Cum se verifică remedierea

      Mislabelled, malformed and double-extension files are rejected, valid images still upload, and stored uploads cannot run as code.

  7. F-07MediuNo HTTPS-only policy (HSTS)Transport
  8. F-08MediuNo content security policyBrowser
  9. F-09MediuEmail authentication lacks DMARC and DKIMEmail
  10. F-19MediuAsset-style URLs cause HTML pages to be cachedCaching
  11. F-10ScăzutUnexpected parameter types cause server errorsInput
  12. F-11ScăzutLegacy TLS 1.0 and 1.1 are still acceptedTransport
  13. F-12ScăzutA pre-login cookie has no explicit SameSite policySessions
  14. F-13ScăzutDNS assurance (CAA and DNSSEC) is not publishedDNS
  15. F-14ScăzutBackend error pages disclose the server versionDisclosure
  16. F-15ScăzutA legacy integration endpoint returns an origin errorCMS
  17. F-20ScăzutUnpublished article IDs are distinguishableContent
  18. F-16InfoPage fragments can be requested directlyDisclosure
  19. F-17InfoSecurity baselines differ between the two hostsConfiguration
  20. F-18InfoPublic assets expose software version hintsDisclosure
  21. F-21InfoUpload folders give distinguishable responsesDisclosure
  22. F-22InfoPublic contact addresses can be recovered by scriptsEmail

În raportul livrat, fiecare constatare primește această analiză completă, pe pagina ei.

05Plan de remediere

Ce se repară, în ordine

  1. 01Primele 72 de ore

    Acum

    3constatări
    • Prove the runtime and CMS versions, stage the security updates and record the build after restart.
    • Check where uploads land and what may run there. Reject non-image content.
  2. 02Prima săptămână

    Apoi

    4constatări
    • Close the login bypass, add MFA and bounded throttling.
    • Agree which API fields are public. Confirm every mail sender, then roll out DMARC.
  3. 03În 30 de zile

    Mai târziu

    15constatări
    • Redirect to HTTPS, stage HSTS, test a content policy, retire legacy TLS and fix path caching.
    • Tidy input handling, cookies, DNS assurance and banners as planned maintenance.

06Observații pozitive

Ce a rezistat

Încercate pe rutele examinate. Niciuna confirmată.

  • SQL injectionCurat
  • Reflected cross-site scriptingCurat
  • Stored cross-site scriptingCurat
  • File inclusion and path traversalCurat
  • Open redirectCurat
  • Permissive cross-origin accessCurat
  • Header injectionCurat
  • Server-side request forgeryCurat
  • Host-header and cache poisoningCurat
  • Directory listingSecurizat
  • Sensitive file exposureSecurizat
  • ClickjackingAcoperit

Test de penetrare black-box

Vrei acest raport pentru site-ul tău?

Aceeași metodă, aceeași profunzime, scopul tău. Fiecare constatare ordonată, explicată și cu remedierea ei.

Test de penetrare black‑box

$500

  • Rezumat executiv
  • Constatări
  • Plan de remediere
  • Ce a rezistat