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.
Test de penetrare și evaluare de securitate
- Pregătit pentru
- Evaluare
- Externă, neautentificată
- Raport
- Raportul A, 41 de paginiRaportul B, 59 de pagini
- Referință
- 3Ridicat
- 7Mediu
- 7Scăzut
- 5Info
- 0Ridicat
- 11Mediu
- 10Scăzut
- 7Info
ConfidențialPagina 1 din 41Pagina 1 din 59
Alege un raport
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
- 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ă
- 01DNS and certificate reconnaissance
- 02Content and route discovery
- 03Parameter and injection testing
- 04Header and cookie review
- 05TLS protocol checks
- 06API enumeration
- 07Upload validation
- 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
- 01
Web firewall and edge
Public HTTP and TLS entry point for both hosts.
- 02
Public website
Dynamic pages, search, filters and a public submission form with uploads.
- 03
API and CMS host
Content API, the editors' login and integration endpoints.
- 04
Email domain
Sender policy, signing keys and DNS assurance records.
04Registrul constatărilor
22 de constatări, ordonate
22 din 22
- F-01RidicatServer runtime needs urgent patch verificationServer
F-02RidicatAnonymous API access exposes the content archive and contact dataAPIAnaliză completă
7.5CVSS 3.1estimatConfirmedPe î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 fieldsAcț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.
Cum se verifică remedierea
Compare anonymous API responses with the agreed publication rules. Private fields are withheld; public pages still work.
- F-03RidicatCMS core is behind the current security releaseCMS
F-04MediuA trailing slash bypasses the login-page blockSign-inAnaliză completă
5.3CVSS 3.1estimatObservedPe î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 ForbiddenAcț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.
Cum se verifică remedierea
Every equivalent login address gets the same decision, and real editors can still sign in.
- F-05MediuLogin form has no observed throttlingSign-in
F-06MediuUpload form accepts falsely labelled image filesUploadsAnaliză completă
5.4CVSS 3.1estimatValidation failurePe î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 limitAcț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.
Cum se verifică remedierea
Mislabelled, malformed and double-extension files are rejected, valid images still upload, and stored uploads cannot run as code.
- F-07MediuNo HTTPS-only policy (HSTS)Transport
- F-08MediuNo content security policyBrowser
- F-09MediuEmail authentication lacks DMARC and DKIMEmail
- F-19MediuAsset-style URLs cause HTML pages to be cachedCaching
- F-10ScăzutUnexpected parameter types cause server errorsInput
- F-11ScăzutLegacy TLS 1.0 and 1.1 are still acceptedTransport
- F-12ScăzutA pre-login cookie has no explicit SameSite policySessions
- F-13ScăzutDNS assurance (CAA and DNSSEC) is not publishedDNS
- F-14ScăzutBackend error pages disclose the server versionDisclosure
- F-15ScăzutA legacy integration endpoint returns an origin errorCMS
- F-20ScăzutUnpublished article IDs are distinguishableContent
- F-16InfoPage fragments can be requested directlyDisclosure
- F-17InfoSecurity baselines differ between the two hostsConfiguration
- F-18InfoPublic assets expose software version hintsDisclosure
- F-21InfoUpload folders give distinguishable responsesDisclosure
- 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
- 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.
- 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.
- 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
01Rezultatele evaluăriiRaportul B
Securitatea dintr-o privire
Risc general
Mediu
Evaluat mediu: nimic critic sau ridicat. De lucrat: disponibilitatea, costul cererilor și accesul la director.
Constatări după gravitate
28 constatări
- 11constatări ridicate și medii de rezolvat întâi
- 59pagini în raportul livrat
- 18clase de atac care au rezistat
02Rezumat executiv
Ce citește proprietarul întâi
The core application held up. The work is availability, request cost and how much of the directory a script can collect.
Implicații pentru afacere
An alternate hostname serves blank pages. Search and asset delivery make automated collection cheap and repeat traffic expensive. Email impersonation is only monitored, not blocked.
Priorități imediate
Fix hostname routing and monitor real content. Cut uncached repeat fetches, set request budgets and agree what the directory publishes. Stage HTTPS-only and email enforcement.
Controale care au rezistat
Output encoding, method limits, body limits and strict JSON validation resisted every tested attack. Framing is blocked. Concurrent duplicate submissions were handled correctly.
03Scop și metodologie
Ce s-a testat și cum
- Țintă
- A creative directory website with search, profiles and a JSON route
- Test
- External black-box penetration test
- Acces
- Unauthenticated, no source code or accounts
- Fereastră
- A single testing window
Metodă
- 01DNS and TLS reconnaissance
- 02Route and parameter discovery
- 03Injection, encoding and method checks
- 04Request-parsing checks
- 05Search and JSON enumeration
- 06Browser header review
- 07Form validation
- 08Bounded rate and connection measurements
În scop
- Public website
- Alternate hostname
- JSON and form endpoints
- TLS endpoints
- DNS and email domain records
Reguli de angajare
- No existing record, file or setting was edited or deleted
- The public form was exercised with test identities only
- Rate and connection trials kept bounded
- Directory data came from public endpoints only
În afara scopului
- The edge provider's infrastructure
- Their mail provider
- Server administration
- Signed-in testing
- Denial-of-service load
Limite declarate
- Effects on the origin's bandwidth cannot be measured from outside
- Rate results reflect one testing window
- No login or upload interface was found to test
Suprafața de atac
- 01
Web firewall and edge
Public HTTP and TLS entry point, in front of a reverse proxy.
- 02
Public website
Search, profile pages and discovery files.
- 03
JSON and form endpoints
A search route that answers in JSON and one documented write form.
- 04
Email domain
Sender policy, signing keys and DNS assurance records.
04Registrul constatărilor
28 de constatări, ordonate
28 din 28
- F-01MediuNo HTTPS-only policy (HSTS)Transport
- F-02MediuDMARC monitors impersonation but does not block itEmail
- F-03MediuNo certificate-authority restriction (CAA)DNS
- F-04MediuSearch showed no throttling in a burst testAbuse
- F-05MediuNumeric profile links make the directory easy to walkDirectory
- F-10MediuUnfinished requests hold connections until a timeoutConnections
F-13MediuAn alternate hostname serves blank pagesAvailabilityAnaliză completă
MediuTipAvailability defectConfirmedPe înțelesul tuturor
Visitors who use the other common form of the address get a successful response with nothing on it, and no redirect to the working site.
Implicații pentru afacere
Those visitors hit a dead end. Uptime checks that only read the status code miss it, and search engines see an empty page instead of the real one.
Ce arată dovezile
Repeated homepage requests on the alternate hostname returned success with an empty body. Search, profile, asset and discovery paths did the same. Sending the main hostname in the request header brought the content back, so the fault sits in routing for that one hostname.
Cereri capturate, generalizate GET main host / 200 full pageGET alternate host / 200 empty bodyGET alternate host / 200 empty bodyGET alternate, main Host 200 full pageAcțiune recomandată
Redirect the alternate hostname to the main one with path and query kept, or route it to the same application. Add a content check to monitoring.
Cum se verifică remedierea
Homepage, search, profile and asset links on the alternate hostname reach real content, and a monitor flags an empty successful response.
- F-14MediuA forwarded visitor-IP header triggers an edge blockIntegration
F-20MediuStatic assets bypass browser and edge cachesCachingAnaliză completă
MediuTipAvailability and performanceConfirmedPe înțelesul tuturor
Stylesheets, icons and other common files are downloaded in full on every visit instead of being reused. Some media is cached. The main static bundle is not.
Implicații pentru afacere
Repeat visits cost more bandwidth and server work. With no throttling in front, it also gives anyone a cheap way to make the server do expensive work.
Ce arată dovezile
Repeated stylesheet requests were never served from the edge cache; repeated media requests were. A unique query string on a cached media file forced a full uncached copy. Two serving layers sent overlapping cache headers.
Cereri capturate, generalizate GET stylesheet, repeated edge: not cachedGET media file, repeated edge: cachedGET media file + new query edge: miss, full bodyAcțiune recomandată
Set caching by resource type: long, immutable caching only for versioned file names, validators and a sensible freshness period for the rest. Check edge rules, cache keys and app headers together.
Cum se verifică remedierea
Cold and warm requests show cache hits or not-modified responses where expected, and changing a file still refreshes it.
- F-23MediuSearch pages continue past the published limitDirectory
F-28MediuAn undocumented JSON route allows bulk directory downloadDirectoryAnaliză completă
MediuTipDirectory access policyConfirmedPe înțelesul tuturor
A JSON search route returns profile names, links, aliases and platform links in a format scripts can collect page by page.
Implicații pentru afacere
Copying the whole directory takes little effort, and the copy is a ready list for impersonation or unwanted contact. Access rules need to cover every format the directory is published in.
Ce arată dovezile
Anonymous requests returned paged records with a running total, and paging continued to the end of the directory. The records held no email addresses, phone numbers or postal addresses.
Cereri capturate, generalizate GET /?page=1 200 records, total, next pageGET /?page=2 200 next recordsGET /?page=last 200 final records, no sign-inAcțiune recomandată
Decide who this route is for and which fields it returns. Document it as a public API, or put it behind the intended access control. Add pagination and request limits.
Cum se verifică remedierea
Anonymous responses match the agreed fields and access policy, and request limits apply to the JSON route and public search alike.
- F-06ScăzutDNS answers are not signed (DNSSEC)DNS
- F-07ScăzutOptional browser isolation headers are missingBrowser
- F-08ScăzutPublic metrics reveal overall traffic volumeDisclosure
- F-09ScăzutValidation errors return a full page, not a short messageInput
- F-11ScăzutSeveral held-open connections were accepted at onceConnections
- F-15ScăzutStatic files lack revalidation headersCaching
- F-17ScăzutForm rate limiting behaves differently between runsRate limits
- F-21ScăzutAn oversized image is shown as a small iconPerformance
- F-22ScăzutTrailing-slash and case handling differ between routesRouting
- F-26ScăzutSearch totals understate the real result countSearch
- F-12InfoInput limits and malformed-request handling workedPositive
- F-16InfoCertificate revocation follows the issuer's current modelCertificates
- F-18InfoArray-style query parameters are silently ignoredInput
- F-19InfoRecent profiles are missing from the sitemapPublishing
- F-24InfoCache policy is set by more than one layerConfiguration
- F-25InfoForm validation handles international text and bad JSON safelyPositive
- F-27InfoDuplicate form submissions are handled atomicallyPositive
În raportul livrat, fiecare constatare primește această analiză completă, pe pagina ei.
05Scenarii de atac
Ce am încercat și ce am măsurat
- 01Confirmat
Cache bypass multiplies serving work
- Încercat
- Requested a cached media file with a fresh query string each time, at rising concurrency.
- Măsurat
- Every request missed the cache. A tiny request pulled back a response hundreds of times its size, and throughput kept rising with no throttling.
- Rezultat
- Confirmed. Fix the cache key and set request budgets first.
- 02Confirmat
Walking the directory
- Încercat
- Paged through public search results in order, without signing in.
- Măsurat
- A dozen requests returned a couple of hundred unique profiles. The whole directory was a few hundred requests away.
- Rezultat
- Confirmed. Agree what the directory publishes, then limit every format.
- 03Confirmat
Hostname and forwarded headers
- Încercat
- Requested the alternate hostname, and sent a forwarded visitor-IP header the edge reserves for itself.
- Măsurat
- The alternate hostname returned empty pages every time. The forwarded header made the edge refuse the request.
- Rezultat
- Availability defects. Neither opened a way past the firewall.
- 04A rezistat
Holding connections open
- Încercat
- Opened requests that announce a body and never send it, in growing batches.
- Măsurat
- The edge timeout cut each one off. While they were held, every ordinary request still succeeded.
- Rezultat
- Held up. The timeout bounds the exposure.
06Plan de remediere
Ce se repară, în ordine
- 01Prima săptămână
Apoi
7constatări- Restore hostname routing with paths kept, and monitor for empty pages.
- Set request budgets and one cache policy, and resize the oversized icon.
- Stage HSTS. Confirm every mail sender, then enforce DMARC.
- 02În 30 de zile
Mai târziu
10constatări- Agree which directory fields, limits and formats are public.
- Coordinate CAA and DNSSEC with certificate renewal.
- Document request deadlines, limiter behaviour and header forwarding.
- 03Mentenanță planificată
Întreținere
11constatări- Make browser features, metrics access and error pages deliberate.
- Fix validators, parameters, sitemaps and route variants. Keep the working checks as regression tests.
07Observații pozitive
Ce a rezistat
Încercate pe rutele examinate. Niciuna confirmată.
- Reflected cross-site scriptingCurat
- Stored cross-site scriptingCurat
- SQL injectionCurat
- NoSQL injectionCurat
- Template injectionCurat
- File inclusion and path traversalCurat
- Server-side request forgeryCurat
- Header injectionCurat
- Open redirectCurat
- Permissive cross-origin accessCurat
- Cache poisoning and deceptionCurat
- Request smugglingCurat
- Host-header injectionCurat
- Subdomain takeoverCurat
- Request body limit bypassSecurizat
- Error-page disclosureSecurizat
- ClickjackingAcoperit
- MIME sniffingAcoperit
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


